From: Richard Biener <rguenther@suse.de>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: Jakub Jelinek <jakub@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] tree-optimization/109304 - properly handle instrumented aliases
Date: Tue, 11 Apr 2023 08:21:08 +0000 (UTC) [thread overview]
Message-ID: <nycvar.YFH.7.77.849.2304110818570.4466@jbgna.fhfr.qr> (raw)
In-Reply-To: <ZCv4oib2QS8daYj/@kam.mff.cuni.cz>
On Tue, 4 Apr 2023, Jan Hubicka wrote:
> > On Tue, Apr 04, 2023 at 01:21:40AM +0200, Jan Hubicka via Gcc-patches wrote:
> > > It is however really side case and I am worried about dropping
> > > pure/const from builtin declarations...
> >
> > Yeah, that can certainly break stuff. See e.g. the recently fixed
> > ICE when memcmp wasn't pure in PR109258.
>
> Yep, i think itis better to poke about this in stage1 (it is a can of
> worms). Clearly we have conflict here: if memcmp is implemented locally
> one can construct a testcase where profile would be rejected on
> -fprofile-use time if const flag is not cleared :(. But it should be
> rare thing happening in practice.
If we have a locally implemented memcmp then calls to it shouldn't
be marked 'built-in' ... But then when the compiler itself
creates a memcmp call it would need to resolve to a not instrumented
library copy, or alternatively we should tell the compiler it cannot
emit such a call (but for some builtins not being able to emit them
might prove interesting).
Richard.
next prev parent reply other threads:[~2023-04-11 8:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 7:20 Richard Biener
2023-04-03 23:21 ` Jan Hubicka
2023-04-04 8:26 ` Jakub Jelinek
2023-04-04 10:14 ` Jan Hubicka
2023-04-11 8:21 ` Richard Biener [this message]
2023-04-11 8:15 ` Richard Biener
2023-04-14 19:12 ` Jan Hubicka
2023-04-17 6:35 ` Richard Biener
2023-04-18 16:18 ` Jan Hubicka
-- strict thread matches above, loose matches on Subject: below --
2023-03-28 8:06 Richard Biener
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=nycvar.YFH.7.77.849.2304110818570.4466@jbgna.fhfr.qr \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=jakub@redhat.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).