public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gcc.ourteddybear at xoxy dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/48470] New: ICE in expand_expr_addr_expr_1 at expr.c:6835
Date: Tue, 05 Apr 2011 19:41:00 -0000	[thread overview]
Message-ID: <bug-48470-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: ICE in expand_expr_addr_expr_1 at expr.c:6835
           Product: gcc
           Version: 4.4.5
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: gcc.ourteddybear@xoxy.net


Created attachment 23886
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23886
Proprocessed source (built with -E, since -save-temps is an unrecognized
option)

Version (output from --version, since -v is apparently a verbose flag, not a
version flag):

GNU C (GCC) version 4.4.5 (arm-unknown-elf)
        compiled by GNU C version 3.4.4 (mingw special), GMP version 4.3.2,
MPFR
 version 2.4.2.
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072


Command line:

"C:/Program Files/Rowley Associates Limited/CrossWorks for ARM 2.0/gcc/bin/cc1"
-fmessage-length=0 -mcpu=arm7tdmi -mthumb-interwork -mlittle-endian -mfpu=vfp
-mfloat-abi=soft -nostdinc "-isystemC:/Program Files/Rowley Associates
Limited/CrossWorks for ARM 2.0/include" "-isystemC:/Documents and
Settings/sacleary/Local Settings/Application Data/Rowley Associates
Limited/CrossWorks for ARM/packages/include" "-IC:/Code/v2/LN-200
IMU/../Components/include/FreeRTOS" "-IC:/Code/v2/LN-200
IMU/../Components/include/lwIP" "-IC:/Code/v2/LN-200
IMU/../Components/include/lwIP/ipv4" "-IC:/Code/v2/LN-200
IMU/../Components/include/lwIP glue" -I. "-IC:/Code/v2/LN-200
IMU/../Components/include" "-IC:/Code/v2/LN-200 IMU/../Common"
-D__ARM_ARCH_4T__ -D__CROSSWORKS_ARM -D__CROSSWORKS_MAJOR_VERSION=2
-D__CROSSWORKS_MINOR_VERSION=0 -D__CROSSWORKS_REVISION=8
-D__TARGET_PROCESSOR=AT91SAM7X256 -DOSCILLATOR_CLOCK_FREQUENCY=18432000
"-DBOARDINIPATH = "imu.ini"" "-DdefaultIPAddr = 0x0006000A" "-DdefaultCANAddr =
0x00100600" "-DdefaultMacAddrA = 0x06" "-DBOARD_ID = BOARD_TYPE_LN200"
"-D_DRIVES = 1" -D__THUMB -D__FLASH_BUILD -DNDEBUG -DSAM7_GCC -DTHUMB_INTERWORK
-DSUPERVISOR_START -DSMARTPIGHARDWARE -MD "FPGA ISR.d" -MQ "FPGA ISR.o" -Werror
-quiet -g1 -Wall -Wextra -Wstrict-prototypes -Wmissing-prototypes
-Wmissing-declarations -fms-extensions -O1 -fno-dwarf2-cfi-asm -fno-builtin
"C:/Code/v2/LN-200 IMU/FPGA ISR.c"


             reply	other threads:[~2011-04-05 19:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-05 19:41 gcc.ourteddybear at xoxy dot net [this message]
2011-04-05 22:30 ` [Bug c/48470] " mikpe at it dot uu.se
2011-04-06 19:48 ` [Bug middle-end/48470] " mikpe at it dot uu.se
2011-07-26 15:57 ` gcc.ourteddybear at xoxy dot net
2015-08-03 19:35 ` law at gcc dot gnu.org
2015-08-03 19:36 ` law at redhat dot com

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-48470-4@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: 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).