public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/10719: invalid code generated (x86, "int $5") with __builtin_va_arg(va, char);
Date: Mon, 12 May 2003 14:46:00 -0000	[thread overview]
Message-ID: <20030512144601.27370.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/10719; it has been noted by GNATS.

From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: sbiallas@online-club.de
Cc: rth@gcc.gnu.org, gcc-bugs@gcc.gnu.org, sb@biallas.net, 
    gcc-gnats@gcc.gnu.org
Subject: Re: c/10719: invalid code generated (x86, "int $5") with
 __builtin_va_arg(va, char);
Date: Mon, 12 May 2003 15:45:24 +0100 (BST)

 On Mon, 12 May 2003 sbiallas@online-club.de wrote:
 
 > I can't agree with this: gcc shouldn't generate
 > invalid code on purpose. It knows there is an
 > error and should generate an error and not a
 > warning. The warning is misleading (it sounds like
 > gcc found a problem and corrected it) and will
 > probably not recognized.
 
 Please read the response to Defect Report #109.  This code only yields 
 undefined behavior if it is ever executed, and it might not be, so GCC 
 must not yield an error.  To quote the response:
 
    A conforming implementation must not fail to translate a strictly
    conforming program simply because _some_ possible execution of that
    program would result in undefined behavior.
 
 http://std.dkuug.dk/JTC1/SC22/WG14/www/docs/dr_109.html
 
 -- 
 Joseph S. Myers
 jsm28@cam.ac.uk


             reply	other threads:[~2003-05-12 14:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-12 14:46 Joseph S. Myers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-12 13:56 sbiallas
2003-05-12  3:03 rth
2003-05-09 20:46 Andrew Pinski
2003-05-09 20:36 sb

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=20030512144601.27370.qmail@sources.redhat.com \
    --to=jsm28@cam.ac.uk \
    --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: 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).