public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ghazi@caip.rutgers.edu To: gcc-gnats@gcc.gnu.org Cc: mark@codesourcery.com Subject: middle-end/10540: mips-sgi-irix6.5 testsuite failure in gcc.c-torture/execute/20020227-1.c with checking enabled Date: Tue, 29 Apr 2003 14:36:00 -0000 [thread overview] Message-ID: <20030429143518.14393.qmail@sources.redhat.com> (raw) >Number: 10540 >Category: middle-end >Synopsis: mips-sgi-irix6.5 testsuite failure in gcc.c-torture/execute/20020227-1.c with checking enabled >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Tue Apr 29 14:36:02 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Kaveh Ghazi >Release: gcc version 3.3 20030429 (prerelease) >Organization: >Environment: mips-sgi-irix6.5 >Description: With the 3.3 branch, I'm getting new testsuite failures with checking enabled on mips-sgi-irix6.5 in gcc.c-torture/execute/20020227-1.c. The errors did NOT happen in a 4/23 version: http://gcc.gnu.org/ml/gcc-testresults/2003-04/msg01502.html But they DO happen in a 4/26 version: http://gcc.gnu.org/ml/gcc-testresults/2003-04/msg01636.html I'll try and narrow it down a bit more. >How-To-Repeat: Configure with --enable-checking and target mips-sgi-irix6.5 and compile 20020227-1.i with: cc1 -fpreprocessed 20020227-1.i -quiet -dumpbase 20020227-1.c -auxbase 20020227-1 -version -o 20020227-1.s # 1 "20020227-1.c" # 1 "<built-in>" # 1 "<command line>" # 1 "20020227-1.c" typedef __complex__ float cf; struct x { char c; cf f; } __attribute__ ((__packed__)); extern void f2 (struct x*); extern void f1 (void); int main (void) { f1 (); exit (0); } void f1 (void) { struct x s; s.f = 1; s.c = 42; f2 (&s); } void f2 (struct x *y) { if (y->f != 1 || y->c != 42) abort (); } >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2003-04-29 14:36 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030429143518.14393.qmail@sources.redhat.com \ --to=ghazi@caip.rutgers.edu \ --cc=gcc-gnats@gcc.gnu.org \ --cc=mark@codesourcery.com \ /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).