http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49125
Summary: [avr-gcc] internal compiler error: in build_unary_op,
at c-typeck.c:3786
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo: unassig...@gcc.gnu.org
ReportedBy: ddavenp...@walchem.com
Created attachment 24336
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24336
The preprocessed file that fails.
While compiling avr-libc, the following error message was generated:
dtostre.c: In function 'dtostre':
dtostre.c:63:2: internal compiler error: in build_unary_op, at c-typeck.c:3786
Please submit a full bug report,
The command line and output with -v -save-temps added:
avr-gcc -v -save-temps -DHAVE_CONFIG_H -g -Wall -W -Wstrict-prototypes
-mmcu=avr2 -D__COMPILING_AVR_LIBC__ -mcall-prologues -Os -MT dtostre.o -MD
-MP -MF -c -o dtostre.o dtostre.c -I../../include -I../../common
Using built-in specs.
COLLECT_GCC=avr-gcc
COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/avr/4.6.0/lto-wrapper
Target: avr
Configured with: ../configure --target=avr --enable-languages=c,c++
--disable-nls --disable-libssp
Thread model: single
gcc version 4.6.0 (GCC)
COLLECT_GCC_OPTIONS='-v' '-save-temps' '-D' 'HAVE_CONFIG_H' '-g' '-Wall'
'-Wextra' '-Wstrict-prototypes' '-mmcu=avr2' '-D' '__COMPILING_AVR_LIBC__'
'-mcall-prologues' '-Os' '-MT' 'dtostre.o' '-MD' '-MP' '-MF' '-c' '-o'
'dtostre.o' '-I' '../../include' '-I' '../../common'
/usr/local/libexec/gcc/avr/4.6.0/cc1 -E -quiet -v -I ../../include -I
../../common -MD dtostre.d -MF -c -MP -MT dtostre.o -D HAVE_CONFIG_H -D
__COMPILING_AVR_LIBC__ dtostre.c -mmcu=avr2 -mcall-prologues -Wall -Wextra
-Wstrict-prototypes -g -fworking-directory -Os -fpch-preprocess -o dtostre.i
ignoring nonexistent directory
"/usr/local/lib/gcc/avr/4.6.0/../../../../avr/sys-include"
ignoring nonexistent directory
"/usr/local/lib/gcc/avr/4.6.0/../../../../avr/include"
#include "..." search starts here:
#include <...> search starts here:
../../include
../../common
/usr/local/lib/gcc/avr/4.6.0/include
/usr/local/lib/gcc/avr/4.6.0/include-fixed
End of search list.
COLLECT_GCC_OPTIONS='-v' '-save-temps' '-D' 'HAVE_CONFIG_H' '-g' '-Wall'
'-Wextra' '-Wstrict-prototypes' '-mmcu=avr2' '-D' '__COMPILING_AVR_LIBC__'
'-mcall-prologues' '-Os' '-MT' 'dtostre.o' '-MD' '-MP' '-MF' '-c' '-o'
'dtostre.o' '-I' '../../include' '-I' '../../common'
/usr/local/libexec/gcc/avr/4.6.0/cc1 -fpreprocessed dtostre.i -quiet -dumpbase
dtostre.c -mmcu=avr2 -mcall-prologues -auxbase dtostre -g -Os -Wall -Wextra
-Wstrict-prototypes -version -o dtostre.s
GNU C (GCC) version 4.6.0 (avr)
compiled by GNU C version 4.2.1 (Apple Inc. build 5664), GMP version 4.3.2,
MPFR version 2.4.2, MPC version 0.8.1
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
GNU C (GCC) version 4.6.0 (avr)
compiled by GNU C version 4.2.1 (Apple Inc. build 5664), GMP version 4.3.2,
MPFR version 2.4.2, MPC version 0.8.1
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
Compiler executable checksum: b184bfbe78c726ac0be514e297f61b46
dtostre.c: In function 'dtostre':
dtostre.c:63:2: internal compiler error: in build_unary_op, at c-typeck.c:3786
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
*** end of compiler output ***
The above command was simplified from the original command line as created by
the makefile. I removed a few redundant -I parameters, and added the -v
-save-temps for this report. The above command generates the same error message
as originally spotted while building the library.
avr-gcc build configuration parameters:
Using built-in specs.
COLLECT_GCC=avr-gcc
COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/avr/4.6.0/lto-wrapper
Target: avr
Configured with: ../configure --target=avr --enable-languages=c,c++
--disable-nls --disable-libssp
Thread model: single
gcc version 4.6.0 (GCC)
This is running on OSX 10.6.6 (i686-apple-darwin10.6.0).
The expected behavior is to compile without error, or at least without an
internal compiler error. As the code in question is not code I wrote, I can not
vouch for it being bug free. However, I did review the code file and did not
notice a issue with the line in question of the variables used at or near that
line.
