mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Cc: Georg Sauthoff <mail@georg.so>
Subject: Re: memchr() performance
Date: Mon, 19 Sep 2016 19:58:48 +0200	[thread overview]
Message-ID: <20160919175847.GA1280@port70.net> (raw)
In-Reply-To: <20160919132953.GA8375@dell12.lru.li>

* Georg Sauthoff <mail@georg.so> [2016-09-19 15:29:53 +0200]:
> 
> Yes. Sure, ub means that anything can happen, but this case should be ok
> with GCC - if the function is compiled in isolation in its own
> translation unit.
> 

unless you use lto

(which musl does not support now, but ppl are doing this)


  parent reply	other threads:[~2016-09-19 17:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-18 18:54 Georg Sauthoff
2016-09-18 20:40 ` Rich Felker
2016-09-18 20:40 ` Szabolcs Nagy
2016-09-19 13:29   ` Georg Sauthoff
2016-09-19 13:37     ` Rich Felker
2016-09-19 17:58     ` Szabolcs Nagy [this message]
2016-09-20 17:57       ` Georg Sauthoff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160919175847.GA1280@port70.net \
    --to=nsz@port70.net \
    --cc=mail@georg.so \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).