public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/101941] [12 Regression] Linux kernel build failure due to retaining fnsplit fragment with __attribute__((__error__))
Date: Tue, 16 Nov 2021 05:07:21 +0000 [thread overview]
Message-ID: <bug-101941-4-vMl6slHfNs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101941-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101941
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pinskia at gcc dot gnu.org
--- Comment #15 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Created attachment 51805
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51805&action=edit
Untested (not even tried to compile)
(In reply to Andrew Pinski from comment #14)
> * special case function splitting such that a BB that contains a function
> call which has either warning or error attribute on it; not to split out to
> a different function.
Something like this attachment.
next prev parent reply other threads:[~2021-11-16 5:07 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 22:36 [Bug ipa/101941] New: " dmalcolm at gcc dot gnu.org
2021-08-16 22:36 ` [Bug ipa/101941] " dmalcolm at gcc dot gnu.org
2021-08-16 22:50 ` pinskia at gcc dot gnu.org
2021-08-16 23:02 ` [Bug ipa/101941] [12 Regression] " dmalcolm at gcc dot gnu.org
2021-08-17 7:56 ` rguenth at gcc dot gnu.org
2021-08-18 13:47 ` dmalcolm at gcc dot gnu.org
2021-09-16 23:00 ` pinskia at gcc dot gnu.org
2021-09-17 8:47 ` jakub at gcc dot gnu.org
2021-09-17 8:53 ` jakub at gcc dot gnu.org
2021-09-20 8:18 ` dac324 at yahoo dot de
2021-11-15 9:37 ` pinskia at gcc dot gnu.org
2021-11-15 9:43 ` aldyh at gcc dot gnu.org
2021-11-15 10:00 ` pinskia at gcc dot gnu.org
2021-11-15 14:38 ` jakub at gcc dot gnu.org
2021-11-16 4:24 ` pinskia at gcc dot gnu.org
2021-11-16 5:07 ` pinskia at gcc dot gnu.org [this message]
2021-11-16 5:59 ` pinskia at gcc dot gnu.org
2021-11-16 6:14 ` pinskia at gcc dot gnu.org
2021-11-16 6:24 ` pinskia at gcc dot gnu.org
2021-11-16 10:04 ` hubicka at kam dot mff.cuni.cz
2021-11-16 10:23 ` jakub at gcc dot gnu.org
2021-11-16 10:41 ` hubicka at gcc dot gnu.org
2021-11-17 1:12 ` pinskia at gcc dot gnu.org
2021-11-17 3:10 ` pinskia at gcc dot gnu.org
2021-11-17 6:27 ` pinskia at gcc dot gnu.org
2022-01-12 14:17 ` dmalcolm at gcc dot gnu.org
2022-01-13 14:23 ` marxin at gcc dot gnu.org
2022-01-13 14:24 ` marxin at gcc dot gnu.org
2022-01-13 14:29 ` pinskia at gcc dot gnu.org
2022-01-13 15:01 ` siddhesh at gcc dot gnu.org
2022-01-18 10:36 ` cvs-commit at gcc dot gnu.org
2022-01-18 10:36 ` 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-101941-4-vMl6slHfNs@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).