public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/102910] cf-descriptor-5-c.c fails to build
Date: Sun, 24 Oct 2021 18:34:51 +0000 [thread overview]
Message-ID: <bug-102910-4-a4An8vdPIJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102910-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102910
--- Comment #3 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Sun, Oct 24, 2021 at 05:28:08AM +0000, pinskia at gcc dot gnu.org wrote:
>
> --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
> I think the following is better:
>
> #ifndef alloca
> #define alloca __builtin_alloca
> #endif
>
> Instead of the include of alloca.h.
>
I have no preference with regards to the fix. I do
however prefer that when trivially obvious choices
are available that one is selected and committed.
next prev parent reply other threads:[~2021-10-24 18:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-23 23:20 [Bug fortran/102910] New: " kargl at gcc dot gnu.org
2021-10-23 23:21 ` [Bug fortran/102910] " kargl at gcc dot gnu.org
2021-10-23 23:31 ` kargl at gcc dot gnu.org
2021-10-24 5:28 ` [Bug testsuite/102910] " pinskia at gcc dot gnu.org
2021-10-24 18:34 ` sgk at troutmask dot apl.washington.edu [this message]
2021-10-24 18:39 ` kargl at gcc dot gnu.org
2021-10-24 19:31 ` dje at gcc dot gnu.org
2021-10-24 20:59 ` kargl at gcc dot gnu.org
2021-10-24 21:35 ` dje at gcc dot gnu.org
2021-10-25 10:08 ` burnus at gcc dot gnu.org
2021-10-25 17:05 ` sandra at gcc dot gnu.org
2021-10-25 17:53 ` sgk at troutmask dot apl.washington.edu
2021-10-25 18:33 ` sandra at gcc dot gnu.org
2021-10-25 18:48 ` cvs-commit at gcc dot gnu.org
2021-10-26 14:25 ` cvs-commit at gcc dot gnu.org
2021-10-26 14:26 ` sandra at gcc dot gnu.org
2021-10-26 16:40 ` kargl 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-102910-4-a4An8vdPIJ@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).