public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: sbiallas@online-club.de 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 13:56:00 -0000 [thread overview] Message-ID: <20030512135601.28756.qmail@sources.redhat.com> (raw) The following reply was made to PR c/10719; it has been noted by GNATS. From: sbiallas@online-club.de To: rth@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, sb@biallas.net, gcc-gnats@gcc.gnu.org Cc: Subject: Re: c/10719: invalid code generated (x86, "int $5") with __builtin_va_arg(va, char); Date: Mon, 12 May 2003 15:46:55 +0200 (MEST) >Not a bug. This is in fact a feature. As you note, the code >is bad and you should use "int". There is no sensible code >that could be generated. 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. With the same attitude you could easily allow instantiating a class with abstract functions and segv when an abstract function is called. Additionally "int $5" is a very bad way of indicating bad code. This would for example trigger a "print screen" on DOS or could even be a syscall on other systems. Regards, Sebastian
next reply other threads:[~2003-05-12 13:56 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-12 13:56 sbiallas [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-12 14:46 Joseph S. Myers 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=20030512135601.28756.qmail@sources.redhat.com \ --to=sbiallas@online-club.de \ --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).