public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: tau@logos.t.u-tokyo.ac.jp To: gcc-gnats@gcc.gnu.org Subject: c/7026: sparc V9 -mflat -g appears not working Date: Thu, 13 Jun 2002 19:46:00 -0000 [thread overview] Message-ID: <200206140049.JAA08257@jaguar.logos.t.u-tokyo.ac.jp> (raw) >Number: 7026 >Category: c >Synopsis: compiler dies with "internal compiler error" >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu Jun 13 17:56:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Kenjiro Taura >Release: 3.2 >Organization: University of Tokyo >Environment: System: SunOS jaguar 5.8 Generic_108528-06 sun4u sparc SUNW,Ultra-Enterprise Architecture: sun4 host: sparcv9-sun-solaris2 build: sparcv9-sun-solaris2 target: sparcv9-sun-solaris2 configured with: ../gcc-3.0.4/configure --prefix=/home/tau/local/SunOS-5.8-sparc/bin sparcv9-sun-solaris >Description: when the attached file is compiled with "gcc -v -temp-save -g -mflat -Wall os.c", gcc dies with the following output: gcc -v -save-temps -g -mflat -Wall os.c Reading specs from /home/tau/local/gcc-3.1-64-install/lib/gcc-lib/sparcv9-sun-s\ olaris2/3.2/specs Configured with: ../gcc/configure --prefix=/home/tau/local/gcc-3.1-64-install -\ -enable-languages=c,c++ sparcv9-sun-solaris2 Thread model: posix gcc version 3.2 20020613 (experimental) /home/tau/local/gcc-3.1-64-install/lib/gcc-lib/sparcv9-sun-solaris2/3.2/cc1 -E\ -quiet -v -D__GNUC__=3 -D__GNUC_MINOR__=2 -D__GNUC_PATCHLEVEL__=0 -Dsparc -Dsu\ n -Dunix -D__svr4__ -D__SVR4 -D__PRAGMA_REDEFINE_EXTNAME -D__sparc__ -D__sun__ \ -D__unix__ -D__svr4__ -D__SVR4 -D__PRAGMA_REDEFINE_EXTNAME -D__sparc -D__sun -D\ __unix -Asystem=unix -Asystem=svr4 -D__arch64__ -Acpu=sparc64 -Amachine=sparcv9\ -D__sparcv9 os.c -Wall -mflat os.i ignoring nonexistent directory "/home/tau/local/gcc-3.1-64-install/sparcv9-sun-\ solaris2/include" #include "..." search starts here: #include <...> search starts here: /usr/local/include /home/tau/local/gcc-3.1-64-install/include /home/tau/local/gcc-3.1-64-install/lib/gcc-lib/sparcv9-sun-solaris2/3.2/includ\ e /usr/include End of search list. /home/tau/local/gcc-3.1-64-install/lib/gcc-lib/sparcv9-sun-solaris2/3.2/cc1 -f\ preprocessed os.i -quiet -dumpbase os.c -mflat -g -Wall -version -o os.s GNU C version 3.2 20020613 (experimental) (sparcv9-sun-solaris2) compiled by GNU C version 2.95.2 19991024 (release). os.c: In function `f': os.c:6: internal compiler error: Internal compiler error in reg_save, at dwarf2\ out.c:796 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: the above file "os.c" is a small file that includes nothing. Here it is: void g(); void f() { g(); } configure options appear above. >Fix: I have not examined how to fix it for now. The only workarounds which I know of right now are either (1) do not use -mflat, or (2) do not use -g (in this particular case). if we remove either of them, the compiler no longer dies. I really need '-mflat' option, so I would appreciate if it is fixed soon. >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2002-06-14 0:56 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=200206140049.JAA08257@jaguar.logos.t.u-tokyo.ac.jp \ --to=tau@logos.t.u-tokyo.ac.jp \ --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).