public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/65873] [5/6 Regression] Failure to inline always_inline memcpy
Date: Mon, 27 Apr 2015 08:14:00 -0000 [thread overview]
Message-ID: <bug-65873-4-ziMJsE1an5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65873-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65873
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Jan Hubicka from comment #1)
> I think certain combinations of flag will trigger ICE, such as one
> enabling/disabling vector builtins. But I suppose we may want to bypass
> majority of the checks for case we have always_inline w/o explicit
> optimization attribute indeed, but only at early inlining time, probably not
> at LTO?
> At LTO time we already did transformation that turn previously correct code
> with target's optimization flags to be incorrect (i.e. -fstrict-aliasing
> blocks some transformations we may do during early opts)
Yeah, special casing always_inline with no explicit optimize/target attributes
only, and only during early inlining IMHO should be sufficient.
next prev parent reply other threads:[~2015-04-27 8:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 9:55 [Bug ipa/65873] New: " jakub at gcc dot gnu.org
2015-04-24 9:55 ` [Bug ipa/65873] " jakub at gcc dot gnu.org
2015-04-24 9:56 ` jakub at gcc dot gnu.org
2015-04-27 8:05 ` hubicka at gcc dot gnu.org
2015-04-27 8:14 ` jakub at gcc dot gnu.org [this message]
2015-04-27 9:19 ` rguenth at gcc dot gnu.org
2015-04-30 15:09 ` hubicka at gcc dot gnu.org
2015-05-05 7:41 ` jakub at gcc dot gnu.org
2015-05-13 0:09 ` hubicka at gcc dot gnu.org
2015-05-13 2:55 ` hubicka at gcc dot gnu.org
2015-05-13 2:58 ` hubicka at gcc dot gnu.org
2015-05-13 15:51 ` [Bug ipa/65873] [5 " hubicka at gcc dot gnu.org
2015-05-17 17:43 ` hubicka at gcc dot gnu.org
2015-05-23 19:38 ` [Bug ipa/65873] " hubicka at gcc dot gnu.org
2015-07-16 9:17 ` rguenth at gcc dot gnu.org
2022-01-09 0:44 ` pinskia at gcc dot gnu.org
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=bug-65873-4-ziMJsE1an5@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).