public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: naveens@noida.hcltech.com To: gcc-gnats@gcc.gnu.org Subject: target/10236: SH: Failure in gcc/testsuite/gcc.c-torture/execute/va-arg-10.c Date: Thu, 27 Mar 2003 06:16:00 -0000 [thread overview] Message-ID: <20030327055849.14522.qmail@sources.redhat.com> (raw) >Number: 10236 >Category: target >Synopsis: SH: Failure in gcc/testsuite/gcc.c-torture/execute/va-arg-10.c >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-legal-code >Submitter-Id: net >Arrival-Date: Thu Mar 27 06:06:01 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Naveen Sharma >Release: gcc version 3.4 20030325 (experimental) >Organization: >Environment: host: i686-pc-linux-gnu build: i686-pc-linux-gnu target: sh-unknown-elf configured with: ../../combined/configure --target=sh-elf --prefix=/home/naveens/hawk/sh --enable-languages=c --enable-checking=rtl >Description: When the following file in gcc testsuite gcc/testsuite/gcc.c-torture/execute/va-arg-10.c is compiled as follows: ~/hawk/sh/bin/sh-elf-gcc -ml -m3 -O3 -g va-arg-10.c the compiler aborts with the following message: va-arg-10.c: In function `f4': va-arg-10.c:88: internal compiler error: RTL check: expected code `subreg', have `post_inc' in mem_loc_descriptor, at dwarf2out.c:8398 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. >How-To-Repeat: Comopile the TC using "-O3 -g" options. The problem does not occur at O1 or O2 optimization levels. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-03-27 6:06 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-27 6:16 naveens [this message] 2003-05-10 9:26 target/10236: [SH] " Dara Hazeghi
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=20030327055849.14522.qmail@sources.redhat.com \ --to=naveens@noida.hcltech.com \ --cc=gcc-gnats@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).