public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/90256] Optimizer with interrupt routines
[not found] <bug-90256-4@http.gcc.gnu.org/bugzilla/>
@ 2023-01-14 11:43 ` nightstrike at gmail dot com
2023-01-14 11:45 ` pinskia at gcc dot gnu.org
2023-01-14 11:54 ` pinskia at gcc dot gnu.org
2 siblings, 0 replies; 3+ messages in thread
From: nightstrike at gmail dot com @ 2023-01-14 11:43 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90256
nightstrike <nightstrike at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nightstrike at gmail dot com
--- Comment #2 from nightstrike <nightstrike at gmail dot com> ---
This is not target specific (or at least it also happens on x86_64-pc-linux).
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug target/90256] Optimizer with interrupt routines
[not found] <bug-90256-4@http.gcc.gnu.org/bugzilla/>
2023-01-14 11:43 ` [Bug target/90256] Optimizer with interrupt routines nightstrike at gmail dot com
@ 2023-01-14 11:45 ` pinskia at gcc dot gnu.org
2023-01-14 11:54 ` pinskia at gcc dot gnu.org
2 siblings, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-01-14 11:45 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90256
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Easy work around is add to the attribute, noipa.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug target/90256] Optimizer with interrupt routines
[not found] <bug-90256-4@http.gcc.gnu.org/bugzilla/>
2023-01-14 11:43 ` [Bug target/90256] Optimizer with interrupt routines nightstrike at gmail dot com
2023-01-14 11:45 ` pinskia at gcc dot gnu.org
@ 2023-01-14 11:54 ` pinskia at gcc dot gnu.org
2 siblings, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-01-14 11:54 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90256
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The reason why it is target specific is because the attribute interrupt is
target specific and ipa-icf code has no knowledge of it. Basically the x86_64
backend when it sees interrupt attribute it should also add no_icf attribute.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-01-14 11:54 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-90256-4@http.gcc.gnu.org/bugzilla/>
2023-01-14 11:43 ` [Bug target/90256] Optimizer with interrupt routines nightstrike at gmail dot com
2023-01-14 11:45 ` pinskia at gcc dot gnu.org
2023-01-14 11:54 ` pinskia at gcc dot gnu.org
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).