public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Kevin Nomura <nomura@netapp.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/6793: varargs constructor inlined inappropriately. Date: Mon, 03 Jun 2002 13:26:00 -0000 [thread overview] Message-ID: <20020603202601.7728.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/6793; it has been noted by GNATS. From: Kevin Nomura <nomura@netapp.com> To: andrea.latina@to.infn.it, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: optimization/6793: varargs constructor inlined inappropriately. Date: Mon, 03 Jun 2002 13:19:06 -0700 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6793 I hit the same problem with a simpler, plain C testcase. Compile the following at -O2. Fails with gcc 3.1, passes with 3.0.4 and earlier. static void inline chdebug(const char *fmt, ... ) { __builtin_next_arg(fmt); } extern void foo(void); void foo(void) { chdebug("ch_monitor: verifying connection "); }
next reply other threads:[~2002-06-03 20:26 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-06-03 13:26 Kevin Nomura [this message] 2002-06-16 17:35 rth 2002-06-16 21:46 rth
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=20020603202601.7728.qmail@sources.redhat.com \ --to=nomura@netapp.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).