public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dac324 at yahoo dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/102361] Errors compiling Linux kernel 5.14.4 with CONFIG_FORTIFY=y Date: Thu, 16 Sep 2021 13:42:44 +0000 [thread overview] Message-ID: <bug-102361-4-p2kCxEdQRV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102361-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102361 --- Comment #7 from DAC324 <dac324 at yahoo dot de> --- Created attachment 51470 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51470&action=edit File mm/memcontrol.c saved with -save-temps option (2/2)
next prev parent reply other threads:[~2021-09-16 13:42 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-16 9:59 [Bug c/102361] New: " dac324 at yahoo dot de 2021-09-16 10:38 ` [Bug c/102361] " marxin at gcc dot gnu.org 2021-09-16 12:34 ` dac324 at yahoo dot de 2021-09-16 12:36 ` jakub at gcc dot gnu.org 2021-09-16 13:29 ` dac324 at yahoo dot de 2021-09-16 13:29 ` dac324 at yahoo dot de 2021-09-16 13:41 ` dac324 at yahoo dot de 2021-09-16 13:42 ` dac324 at yahoo dot de [this message] 2021-09-16 13:45 ` dac324 at yahoo dot de 2021-09-16 22:57 ` [Bug middle-end/102361] " pinskia at gcc dot gnu.org 2021-09-16 22:57 ` pinskia at gcc dot gnu.org 2021-09-16 22:59 ` [Bug ipa/102361] " pinskia at gcc dot gnu.org 2021-09-16 22:59 ` pinskia at gcc dot gnu.org 2021-09-16 23:00 ` pinskia at gcc dot gnu.org 2021-09-17 7:24 ` [Bug ipa/102361] Errors compiling Linux kernel 5.14 " dac324 at yahoo dot de 2021-09-17 7:41 ` pinskia 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-102361-4-p2kCxEdQRV@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: linkBe 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).