public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "travis at danger dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/13807] New: cc1 segfaults compiling specific thumb code
Date: Thu, 22 Jan 2004 02:48:00 -0000	[thread overview]
Message-ID: <20040122024818.13807.travis@danger.com> (raw)

Summary:

Compiling the attached particular piece of code as thumb at -O2 causes the 
compiler to seg fault inside asm_fprintf. It has been reproduced using gcc 
3.3.2 on cygwin and gcc 3.3.1 on macos x. All were compiled using the same 
options.

Release:
gcc 3.3.2 release

Environment:
Linux version 2.4.22-gentoo-r4 (root@varmit) (gcc version 3.2.3 20030422 
(Gentoo Linux 1.4 3.2.3-r3, propolice)) #1 SMP Sat Jan 10 17:26:16 PST 2004

host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: arm-elf
Configured with: ../gcc-3.3.2/configure --prefix=/usr/local/armdev-3.3.2 --
target=arm-elf --program-prefix=arm-elf- --program-suffix=332 --with-newlib --
enable-languages=c
Thread model: single
gcc version 3.3.2

to repeat (where pco_trace.i is the attached file):
arm-elf-gcc332 -v --save-temps -c -mthumb -fno-builtin -O2 -W -Wall -mthumb-
interwork -fsigned-char -funsigned-bitfields -o pco_trace.o pco_trace.i

output is:
Reading specs from /usr/local/armdev-3.3.2-withsuffix/bin/../lib/gcc-lib/arm-
elf/3.3.2/specs
Configured with: ../gcc-3.3.2/configure --prefix=/usr/local/armdev-3.3.2 --
target=arm-elf --program-prefix=arm-elf- --program-suffix=332 --with-newlib --
enable-languages=c
Thread model: single
gcc version 3.3.2
 /usr/local/armdev-3.3.2-withsuffix/bin/../lib/gcc-lib/arm-elf/3.3.2/cc1 -
fpreprocessed pco_trace.i -quiet -dumpbase pco_trace.i -mthumb -mthumb-
interwork -auxbase-strip pco_trace.o -O2 -W -Wall -version -fno-builtin -
fsigned-char -funsigned-bitfields -o pco_trace.s
GNU C version 3.3.2 (arm-elf)
        compiled by GNU C version 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r3, 
propolice).
GGC heuristics: --param ggc-min-expand=98 --param ggc-min-heapsize=129117
pco_trace.c: In function `read_str2ind_file':
pco_trace.c:147: warning: enumeration value `SCAN_SPACE' not handled in switch
pco_trace.c:58: warning: `fd' might be used uninitialized in this function
pco_trace.c:153: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.

-- 
           Summary: cc1 segfaults compiling specific thumb code
           Product: gcc
           Version: 3.3.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: travis at danger dot com
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: arm-elf


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13807


             reply	other threads:[~2004-01-22  2:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-22  2:48 travis at danger dot com [this message]
2004-01-22  2:48 ` [Bug target/13807] " travis at danger dot com
2004-01-22  8:50 ` pinskia at gcc dot gnu dot org
2004-01-22 20:02 ` travis at danger dot com
2004-01-23 20:03 ` dhazeghi at yahoo dot com
2004-01-23 20:23 ` dhazeghi at yahoo dot com
2004-01-24 12:21 ` rearnsha at arm dot com
2004-01-24 15:23 ` pinskia 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=20040122024818.13807.travis@danger.com \
    --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).