public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/35739] New: [4.3/4.4 regression] ICE with _Decimal128 and va_list
Date: Fri, 28 Mar 2008 19:03:00 -0000 [thread overview]
Message-ID: <bug-35739-1771@http.gcc.gnu.org/bugzilla/> (raw)
The following valid code snippet triggers an ICE since GCC 4.3.0
when compiled with "-fmudflap -O":
=========================================
_Decimal128 foo(int n, ...)
{
int i;
_Decimal128 j;
__builtin_va_list va;
__builtin_va_start(va,n);
for (i = 0; i < n; i++)
j += __builtin_va_arg(va,_Decimal128);
__builtin_va_end(va);
return j;
}
=========================================
bug.c: In function 'foo':
bug.c:2: error: invalid operand to binary operator
<retval>
bug.c:2: internal compiler error: verify_stmts failed
Please submit a full bug report, [etc.]
--
Summary: [4.3/4.4 regression] ICE with _Decimal128 and va_list
Product: gcc
Version: 4.4.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code, monitored
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: reichelt at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35739
next reply other threads:[~2008-03-28 19:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 19:03 reichelt at gcc dot gnu dot org [this message]
2008-03-28 19:04 ` [Bug c/35739] " reichelt at gcc dot gnu dot org
2008-03-30 20:53 ` pinskia at gcc dot gnu dot org
2008-04-01 9:19 ` jakub at gcc dot gnu dot org
2008-04-01 11:12 ` reichelt at gcc dot gnu dot org
2008-04-02 16:21 ` jakub at gcc dot gnu dot org
2008-04-15 9:35 ` jakub at gcc dot gnu dot org
2008-04-15 18:59 ` jakub at gcc dot gnu dot org
2008-04-16 16:03 ` jakub at gcc dot gnu dot org
2008-04-16 16:11 ` jakub at gcc dot gnu dot org
2008-04-16 16:12 ` jakub at gcc dot gnu dot 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-35739-1771@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).