public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janis at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/35713] New: invalid type for va_arg with _Decimal128 Date: Thu, 27 Mar 2008 00:00:00 -0000 [thread overview] Message-ID: <bug-35713-4503@http.gcc.gnu.org/bugzilla/> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1429 bytes --] Using va_arg with _Decimal128 for powerpc-linux results in an error message followed by an ICE, resulting in several new failing GCC tests. This testcase: void foo (int n, ...) { __builtin_va_list ap; _Decimal128 x; __builtin_va_start (ap, n); x = __builtin_va_arg (ap, _Decimal128); __builtin_va_end (ap); } results in these messages: elm3b145% /opt/gcc-nightly/trunk/bin/gcc -c va.c va.c: In function foo: va.c:3: error: type mismatch in binary expression unsigned char unsigned char unsigned int D.1240 = D.1239 | 1 va.c:3: internal compiler error: verify_gimple failed Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. The failure becomes apparent with r133479, but it also happens with earlier GCC sources configured with --enable-checking=types. I plan to continue investigating this problem. -- Summary: invalid type for va_arg with _Decimal128 Product: gcc Version: 4.3.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: target AssignedTo: janis at gcc dot gnu dot org ReportedBy: janis at gcc dot gnu dot org GCC target triplet: powerpc-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35713
next reply other threads:[~2008-03-27 0:00 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-03-27 0:00 janis at gcc dot gnu dot org [this message] 2008-03-29 20:18 ` [Bug target/35713] [4.4 Regression] " pinskia at gcc dot gnu dot org 2008-04-01 17:59 ` janis at gcc dot gnu dot org 2008-04-04 0:22 ` janis at gcc dot gnu dot org 2008-04-05 21:07 ` pinskia at gcc dot gnu dot org 2008-09-18 18:38 ` janis 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-35713-4503@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: 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).