[Bug middle-end/85619] Inconsistent descriptions for new warning options in GCC 8.1.0

[julien at trigofacile dot com via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85619

--- Comment #4 from Julien ÉLIE  ---
Following up on that issue.  I've just checked against GCC 11 documentation.
The two points are still open.
Thanks beforehand.

[Bug middle-end/82798] Inconsistent descriptions for warning options in documentation

[julien at trigofacile dot com via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82798

--- Comment #5 from Julien ÉLIE  ---
Following up on that bug report, I've checked GCC 11 documentation.
Only 3/, part of 5/ (-Wmultistatement-macros) and 6/ have been fixed.
Points 1/, 2/, 4/, part of 5/ (-Wreorder) and 7/ remain.
Thanks beforehand.

[Bug bootstrap/50064] Failure in stage 2 (lazy binding) on openbsd

[julien at trigofacile dot com via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50064

Julien ÉLIE  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #1 from Julien ÉLIE  ---
Probably too old to be worth investigating.
As the author of the bug, I suggest to close it.

[Bug c/83011] -Wformat-truncation=2 difficult to avoid for non-constant bounds

[julien at trigofacile dot com via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83011

--- Comment #8 from Julien ÉLIE  ---
"I do agree that the warning in this case is too difficult to deal with and
should be adjusted so I'm going to confirm this report on that basis."
FWIW, the same warning is still present in GCC 10.2.1.

[Bug c/83011] -Wformat-truncation=2 difficult to avoid for non-constant bounds

[julien at trigofacile dot com via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83011

--- Comment #7 from Julien ÉLIE  ---
*** Bug 103352 has been marked as a duplicate of this bug. ***

[Bug c/103352] Wrong computation of -Wformat-truncation=2

[julien at trigofacile dot com via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103352

Julien ÉLIE  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Julien ÉLIE  ---
Duplicate, sorry.

*** This bug has been marked as a duplicate of bug 83011 ***

[Bug c/103352] New: Wrong computation of -Wformat-truncation=2

[julien at trigofacile dot com via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103352

Bug ID: 103352
   Summary: Wrong computation of -Wformat-truncation=2
   Product: gcc
   Version: 10.2.1
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c
  Assignee: unassigned at gcc dot gnu.org
  Reporter: julien at trigofacile dot com
  Target Milestone: ---

When building
https://raw.githubusercontent.com/InterNetNews/inn/main/lib/timer.c I have a
warning with -Wformat-truncation=2

len = 52 * timer_count + 27 + (prefix == NULL ? 0 : strlen(prefix)) + 1;
buf = xmalloc(len);
if (prefix == NULL)
rc = 0;
else
rc = snprintf(buf, len, "%s ", prefix);

timer.c: In function ‘TMRsummary’:
timer.c:395:36: warning: ‘ ’ directive output may be truncated writing 1 byte
into a region of size between 0 and 1 [-Wformat-truncation=]
  395 | rc = snprintf(buf, len, "%s ", prefix);
  |^
timer.c:395:14: note: ‘snprintf’ output 2 or more bytes (assuming 3) into a
destination of size 1
  395 | rc = snprintf(buf, len, "%s ", prefix);
  |  ^


It seems that "len" is considered to be of length 1.  I bet it comes from the
"+ 1" at the end of the declaration of "len".
If I move the "+ 27" at the end of the declaration of "len", the warning
disappears.

Isn't there something to improve in the way the computation is done for that
warning?

Thanks beforehand.

[Bug middle-end/85619] Inconsistent descriptions for new warning options in GCC 8.1.0

[julien at trigofacile dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85619

--- Comment #3 from Julien ÉLIE  ---
Many thanks, Martin, for willing to take care of it.  (I've also seen your
message in bug 71283.)
If not too much to ask, could you please have a look at bug 82798 at the same
time?

[Bug middle-end/85619] New: Inconsistent descriptions for new warning options in GCC 8.1.0

[julien at trigofacile dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85619

Bug ID: 85619
   Summary: Inconsistent descriptions for new warning options in
GCC 8.1.0
   Product: gcc
   Version: 8.1.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: middle-end
  Assignee: unassigned at gcc dot gnu.org
  Reporter: julien at trigofacile dot com
  Target Milestone: ---

In GCC 8.1.0 documentation
(https://gcc.gnu.org/onlinedocs/gcc-8.1.0/gcc/Warning-Options.html):

1/ -Wif-not-aligned is said to be included by default in documentation, but
Release Changes mention its inclusion in -Wall.  So, is it really the case? 
(Also note a typo "This is is enabled by default." in documentation.)

2/ -Wstringop-truncation and -Wpacked-not-aligned are said to be included in
-Wall in Release Changes but documentation does not mention them in -Wall.

[Bug c/83011] -Wformat-truncation=2 difficult to avoid for non-constant bounds

[julien at trigofacile dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83011

--- Comment #6 from Julien ÉLIE  ---
Many thanks for your kind explanation, Martin.  Perfectly understood.

[Bug c/83011] -Wformat-truncation wrongly computes length (depends on the position of numbers in the addition)

[julien at trigofacile dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83011

--- Comment #4 from Julien ÉLIE  ---
Martin, the following thing still puzzles me.

len = 52 * timer_count + 27 + (prefix == NULL ? 0 : strlen(prefix)) + 1;
=> gives a warning, as explained below

len = 1 + 52 * timer_count + 27 + (prefix == NULL ? 0 : strlen(prefix));
=> gives *no* warning

len = 52 * timer_count + 28 + (prefix == NULL ? 0 : strlen(prefix));
=> gives *no* warning


Isn't there an issue to fix in how the checker assumes the size of the
destination?
I do not understand how such a computation could be a feature.

[Bug c/83011] -Wformat-truncation wrongly computes length (depends on the position of numbers in the addition)

[julien at trigofacile dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83011

--- Comment #2 from Julien ÉLIE  ---
Created attachment 42644
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42644&action=edit
Preprocessed translation unit of timer.c

Thanks Martin for your response.
I attached the result of the following command:
/home/iulius/work/gcc/gcc-7.2.0/bin/gcc -g -O3 -DDEBUG=1 -Wall -Werror -Wextra
-Wformat=2 -Wformat-overflow=2 -Wformat-truncation=2 -Wnull-dereference
-Winit-self -Wmissing-include-dirs -Wshift-overflow=2 -Wsync-nand
-Wstringop-overflow=4 -Wmissing-format-attribute -Walloc-zero -Walloca
-Wduplicated-cond -Wtrampolines -Wshadow -Wpointer-arith -Wc99-c11-compat
-Wbad-function-cast -Wcast-align -Wwrite-strings -Wdangling-else -Wdate-time
-Wjump-misses-init -Wstrict-prototypes -Wold-style-definition
-Wmissing-prototypes -Wmissing-declarations -Wnormalized=nfc -Wrestrict
-Wnested-externs -Winline -Winvalid-pch -Wvla -Wno-unused-function 
-I../include -E timer.c -fPIC -DPIC -o .libs/timer.o

In English, the warning is:

timer.c:395:37: error: ' ' directive output may be truncated writing 1 byte
into a region of size between 0 and 1 [-Werror=format-truncation=]
 rc = snprintf(buf, len, "%s ", prefix);
~ 
timer.c:395:12: note: 'snprintf' output 2 or more bytes (assuming 3) into a
destination of size 1
 rc = snprintf(buf, len, "%s ", prefix);
 ~~~^~~



I'm not using -flto to build the projet.  And, in case it could help, if I add
"-flto" to compiler options, I no longer have the warning.  Is it normal?

[Bug c/83011] New: -Wformat-truncation wrongly computes length (depends on the position of numbers in the addition)

[julien at trigofacile dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83011

Bug ID: 83011
   Summary: -Wformat-truncation wrongly computes length (depends
on the position of numbers in the addition)
   Product: gcc
   Version: 7.2.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c
  Assignee: unassigned at gcc dot gnu.org
  Reporter: julien at trigofacile dot com
  Target Milestone: ---

Hi,

Trying to build INN, I encounter the following warning:

timer.c: Dans la fonction « TMRsummary »:
timer.c:395:37: error: la sortie de la directive «   » peut être tronquée en
écrivant 1 octet dans une région dont la taille est comprise entre 0 et 1
[-Werror=format-truncation=]
 rc = snprintf(buf, len, "%s ", prefix);
~ 
timer.c:395:12: note: « snprintf » écrit 2 octets ou plus (3 supposé) dans une
destination dont la taille est 1
 rc = snprintf(buf, len, "%s ", prefix);
 ~~~^~~


It happens in:
  https://inn.eyrie.org/trac/browser/trunk/lib/timer.c

len = 52 * timer_count + 27 + (prefix == NULL ? 0 : strlen(prefix)) + 1;
buf = xmalloc(len);
off = 0;
if (prefix == NULL)
rc = 0;
else
rc = snprintf(buf, len, "%s ", prefix);


If I rewrite len this way, gcc no longer gives the above warning:

len = 1 + 52 * timer_count + 27 + (prefix == NULL ? 0 : strlen(prefix));


Isn't there a computation issue? (depending on the location of components in
the addition)

Julien

[Bug middle-end/82798] Inconsistent descriptions for warning options in documentation

[julien at trigofacile dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82798

--- Comment #2 from Julien ÉLIE  ---
Other points:

6/ -Wsuggest-final-types and -Wsuggest-final-methods should be mentioned for
C++ (and maybe Objective-C++) only.

7/ -Wc++11-compat and -Wc++14-compat are present in the -Wall list but without
the mention for C++ and Objective-C++.  I believe it should be mentioned.

[Bug web/82798] New: Inconsistent descriptions for warning options in documentation

[julien at trigofacile dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82798

Bug ID: 82798
   Summary: Inconsistent descriptions for warning options in
documentation
   Product: gcc
   Version: 7.2.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: web
  Assignee: unassigned at gcc dot gnu.org
  Reporter: julien at trigofacile dot com
  Target Milestone: ---

In GCC 7 documentation:

1/ One can read "Some options, such as -Wall and -Wextra, turn on other
options, such as -Wunused" and later in the description of -Wunused:  "note
that -Wall implies -Wunused".

However, "-Wunused" is not listed in the list of warning flags turned on by
-Wall.
4 warning flags are instead listed in the -Wall list: -Wunused-function,
-Wunused-label, -Wunused-value and -Wunused-variable.
And 2 warning flags are listed in the -Werror list: -Wunused-parameter,
-Wunused-but-set-parameter.

It seems a bit confusing, and I believe there is something to fix.
Maybe in fact -Wunused is not turned on by -Wall?


2/ -Wuninitialized is listed in both -Wall and -Werror list.
And the description of -Wuninitialized does not mention either of them.
I believe there is something to fix for that.


3/ -Wall should list "-Walloc-size-larger-than=PTRDIFF_MAX" in the warning
flags turned on (according to GCC 7 changes).  The description should mention
that at the same time.


4/ The description of -Wexpansion-to-defined mentions that it is enabled by
-Wextra and -Wpedantic.  The list of warning flags turned on by them should
mention that.


5/ -Wall mentions two warnings that are not described in the documentation:
-Wmultistatement-macros and -Wreorder.  Can they be described please?


Thanks beforehand for fixing these issues.

Julien ÉLIE

[Bug c/51853] MPFR assertion failure with Python: p >= 2 && p <= ((mpfr_prec_t)((mpfr_uprec_t)(~(mpfr_uprec_t)0)>>1))

[julien at trigofacile dot com]

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

--- Comment #3 from Julien ÉLIE  2012-01-14 
08:13:45 UTC ---
Created attachment 26321
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26321
Result of preprocessed file

[Bug c/51853] MPFR assertion failure with Python: p >= 2 && p <= ((mpfr_prec_t)((mpfr_uprec_t)(~(mpfr_uprec_t)0)>>1))

[julien at trigofacile dot com]

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

Julien ÉLIE  changed:

   What|Removed |Added

  Component|target  |c

--- Comment #2 from Julien ÉLIE  2012-01-14 
08:12:29 UTC ---
longobject.i is attached.
Here is the result of "gcc -save-temps":

$ /home/iulius/autobuild/bin/gcc-core-4.6.2/bin/gcc -v -save-temps -pthread -c
-fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes 
-I. -IInclude -I./Include   -DPy_BUILD_CORE -o Objects/longobject.o
Objects/longobject.c
Using built-in specs.
COLLECT_GCC=/home/iulius/autobuild/bin/gcc-core-4.6.2/bin/gcc
COLLECT_LTO_WRAPPER=/home/iulius/autobuild/bin/gcc-core-4.6.2/libexec/gcc/hppa2.0-unknown-linux-gnu/4.6.2/lto-wrapper
Target: hppa2.0-unknown-linux-gnu
Configured with: ../gcc-core-4.6.2-src/configure
--prefix=/home/iulius/autobuild/bin/gcc-core-4.6.2
--with-gmp=/home/iulius/autobuild/bin/gmp-5.0.2
--with-mpfr=/home/iulius/autobuild/bin/mpfr-3.1.0
--with-mpc=/home/iulius/autobuild/bin/mpc-0.9 --disable-nls
--enable-threads=posix --disable-multilib
Thread model: posix
gcc version 4.6.2 (GCC) 
COLLECT_GCC_OPTIONS='-v' '-save-temps' '-pthread' '-c' '-fno-strict-aliasing'
'-g' '-O2' '-D' 'NDEBUG' '-g' '-fwrapv' '-O3' '-Wall' '-Wstrict-prototypes'
'-I' '.' '-I' 'Include' '-I' './Include' '-D' 'Py_BUILD_CORE' '-o'
'Objects/longobject.o'

/home/iulius/autobuild/bin/gcc-core-4.6.2/libexec/gcc/hppa2.0-unknown-linux-gnu/4.6.2/cc1
-E -quiet -v -I . -I Include -I ./Include -D NDEBUG -D Py_BUILD_CORE
Objects/longobject.c -Wall -Wstrict-prototypes -fno-strict-aliasing -fwrapv -g
-g -fworking-directory -O2 -O3 -fpch-preprocess -o longobject.i
ignoring nonexistent directory
"/home/iulius/autobuild/bin/gcc-core-4.6.2/lib/gcc/hppa2.0-unknown-linux-gnu/4.6.2/../../../../hppa2.0-unknown-linux-gnu/include"
ignoring duplicate directory "./Include"
#include "..." search starts here:
#include <...> search starts here:
 .
 Include

/home/iulius/autobuild/bin/gcc-core-4.6.2/lib/gcc/hppa2.0-unknown-linux-gnu/4.6.2/include
 /usr/local/include
 /home/iulius/autobuild/bin/gcc-core-4.6.2/include

/home/iulius/autobuild/bin/gcc-core-4.6.2/lib/gcc/hppa2.0-unknown-linux-gnu/4.6.2/include-fixed
 /usr/include
End of search list.
COLLECT_GCC_OPTIONS='-v' '-save-temps' '-pthread' '-c' '-fno-strict-aliasing'
'-g' '-O2' '-D' 'NDEBUG' '-g' '-fwrapv' '-O3' '-Wall' '-Wstrict-prototypes'
'-I' '.' '-I' 'Include' '-I' './Include' '-D' 'Py_BUILD_CORE' '-o'
'Objects/longobject.o'

/home/iulius/autobuild/bin/gcc-core-4.6.2/libexec/gcc/hppa2.0-unknown-linux-gnu/4.6.2/cc1
-fpreprocessed longobject.i -quiet -dumpbase longobject.c -auxbase-strip
Objects/longobject.o -g -g -O2 -O3 -Wall -Wstrict-prototypes -version
-fno-strict-aliasing -fwrapv -o longobject.s
GNU C (GCC) version 4.6.2 (hppa2.0-unknown-linux-gnu)
compiled by GNU C version 4.6.2, GMP version 5.0.2, MPFR version 3.1.0, MPC
version 0.9
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
GNU C (GCC) version 4.6.2 (hppa2.0-unknown-linux-gnu)
compiled by GNU C version 4.6.2, GMP version 5.0.2, MPFR version 3.1.0, MPC
version 0.9
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
Compiler executable checksum: 6576c6dbf099889f96aaa25f3debe8a2
init2.c:52: MPFR assertion failed: p >= 2 && p <=
((mpfr_prec_t)((mpfr_uprec_t)(~(mpfr_uprec_t)0)>>1))
Objects/longobject.c: In function 'PyLong_FromString':
Objects/longobject.c:1852:43: internal compiler error: Aborted
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.

[Bug c/51853] New: MPFR assertion failure with Python: p >= 2 && p <= ((mpfr_prec_t)((mpfr_uprec_t)(~(mpfr_uprec_t)0)>>1))

[julien at trigofacile dot com]

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

 Bug #: 51853
   Summary: MPFR assertion failure with Python: p >= 2 && p <=
((mpfr_prec_t)((mpfr_uprec_t)(~(mpfr_uprec_t)0)>>1))
Classification: Unclassified
   Product: gcc
   Version: 4.6.2
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c
AssignedTo: unassig...@gcc.gnu.org
ReportedBy: jul...@trigofacile.com


Hi,

Trying to build Python 2.7.2 (and also 3.2.2) with GCC 4.6.2 and MPFR 3.1.0, I
obtain the following error on HP PA-8600 running Debian (it is in
fact gcc61 in the GCC Compile Farm ):

/home/iulius/autobuild/bin/gcc-core-4.6.2/bin/gcc -pthread -c  -DNDEBUG -g
-fwrapv -O3 -Wall -Wstrict-prototypes-I. -IInclude -I./Include   
-DPy_BUILD_CORE -o Objects/longobject.o Objects/longobject.c
init2.c:52: MPFR assertion failed: p >= 2 && p <=
((mpfr_prec_t)((mpfr_uprec_t)(~(mpfr_uprec_t)0)>>1))
Objects/longobject.c: In function 'PyLong_FromString':
Objects/longobject.c:2002:36: internal compiler error: Aborted
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.
make: *** [Objects/longobject.o] Error 1




Configured with: ../gcc-core-4.6.2-src/configure
--prefix=/home/iulius/autobuild/bin/gcc-core-4.6.2
--with-gmp=/home/iulius/autobuild/bin/gmp-5.0.2
--with-mpfr=/home/iulius/autobuild/bin/mpfr-3.1.0
--with-mpc=/home/iulius/autobuild/bin/mpc-0.9 --disable-nls
--enable-threads=posix --disable-multilib


-- 
Julien

[Bug bootstrap/50064] New: Failure in stage 2 (lazy binding) on openbsd

[julien at trigofacile dot com]

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

 Bug #: 50064
   Summary: Failure in stage 2 (lazy binding) on openbsd
Classification: Unclassified
   Product: gcc
   Version: 4.6.1
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: bootstrap
AssignedTo: unassig...@gcc.gnu.org
ReportedBy: jul...@trigofacile.com


Hi,

I am trying to bootstrap GCC 4.6.1 on OpenBSD 4.6 GENERIC#43 sparc64 (it is in
fact gcc64 in the GCC Compile Farm ).
/usr/bin/uname -p = SUNW,UltraSPARC-IIIi (rev 2.4) @ 1002 MHz

Build is initially done with GCC 3.3.5.

Configure flags:
./configure --prefix=/home/iulius/autobuild/bin/gcc-core-4.6.1
--with-gmp=/home/iulius/autobuild/bin/gmp-4.3.2
--with-mpfr=/home/iulius/autobuild/bin/mpfr-2.4.2
--with-mpc=/home/iulius/autobuild/bin/mpc-0.8.1






Checking multilib configuration for libgcc...
Configuring stage 2 in sparc64-unknown-openbsd4.6/libgcc
configure: loading cache ./config.cache
checking for --enable-version-specific-runtime-libs... no
checking for a BSD-compatible install... /usr/bin/install -c
checking for gawk... nawk
checking build system type... sparc64-unknown-openbsd4.6
checking host system type... sparc64-unknown-openbsd4.6
checking for sparc64-unknown-openbsd4.6-ar... ar
checking for sparc64-unknown-openbsd4.6-lipo... lipo
checking for sparc64-unknown-openbsd4.6-nm...
/home/iulius/autobuild/src/gcc-core-4.6.1/host-sparc64-unknown-openbsd4.6/gcc/nm
checking for sparc64-unknown-openbsd4.6-ranlib... ranlib
checking for sparc64-unknown-openbsd4.6-strip... strip
checking whether ln -s works... yes
checking for sparc64-unknown-openbsd4.6-gcc...
/home/iulius/autobuild/src/gcc-core-4.6.1/host-sparc64-unknown-openbsd4.6/gcc/xgcc
-B/home/iulius/autobuild/src/gcc-core-4.6.1/host-sparc64-unknown-openbsd4.6/gcc/
-B/home/iulius/autobuild/bin/gcc-core-4.6.1/sparc64-unknown-openbsd4.6/bin/
-B/home/iulius/autobuild/bin/gcc-core-4.6.1/sparc64-unknown-openbsd4.6/lib/
-isystem
/home/iulius/autobuild/bin/gcc-core-4.6.1/sparc64-unknown-openbsd4.6/include
-isystem
/home/iulius/autobuild/bin/gcc-core-4.6.1/sparc64-unknown-openbsd4.6/sys-include
 
checking for suffix of object files... configure: error: in
`/home/iulius/autobuild/src/gcc-core-4.6.1/sparc64-unknown-openbsd4.6/libgcc':
configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.
gmake[2]: *** [configure-stage2-target-libgcc] Error 1


config.log ->

/home/iulius/autobuild/src/gcc-core-4.6.1/libgcc/configure
--cache-file=./config.cache --enable-multilib
--prefix=/home/iulius/autobuild/bin/gcc-core-4.6.1
--with-gmp=/home/iulius/autobuild/bin/gmp-4.3.2
--with-mpfr=/home/iulius/autobuild/bin/mpfr-2.4.2
--with-mpc=/home/iulius/autobuild/bin/mpc-0.8.1 --enable-languages=c,lto
--program-transform-name=s,y,y, --disable-option-checking
--with-target-subdir=sparc64-unknown-openbsd4.6
--build=sparc64-unknown-openbsd4.6 --host=sparc64-unknown-openbsd4.6
--target=sparc64-unknown-openbsd4.6 --srcdir=../.././libgcc
--with-build-libsubdir=host-sparc64-unknown-openbsd4.6



configure:3055:
/home/iulius/autobuild/src/gcc-core-4.6.1/host-sparc64-unknown-openbsd4.6/gcc/xgcc
-B/home/iulius/autobuild/src/gcc-core-4.6.1/host-sparc64-unknown-openbsd4.6/gcc/
-B/home/iulius/autobuild/bin/gcc-core-4.6.1/sparc64-unknown-openbsd4.6/bin/
-B/home/iulius/autobuild/bin/gcc-core-4.6.1/sparc64-unknown-openbsd4.6/lib/
-isystem
/home/iulius/autobuild/bin/gcc-core-4.6.1/sparc64-unknown-openbsd4.6/include
-isystem
/home/iulius/autobuild/bin/gcc-core-4.6.1/sparc64-unknown-openbsd4.6/sys-include
   -o conftest -g -O2   conftest.c  >&5
/home/iulius/autobuild/src/gcc-core-4.6.1/host-sparc64-unknown-openbsd4.6/gcc/cc1:/home/iulius/autobuild/src/gcc-core-4.6
.1/host-sparc64-unknown-openbsd4.6/gcc/cc1: undefined symbol ''
lazy binding failed!
cc1: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.
configure:3058: $? = 1
configure:3246: checking for suffix of object files
configure:3268:
/home/iulius/autobuild/src/gcc-core-4.6.1/host-sparc64-unknown-openbsd4.6/gcc/xgcc
-B/home/iulius/autobuild/src/gcc-core-4.6.1/host-sparc64-unknown-openbsd4.6/gcc/
-B/home/iulius/autobuild/bin/gcc-core-4.6.1/sparc64-unknown-openbsd4.6/bin/
-B/home/iulius/autobuild/bin/gcc-core-4.6.1/sparc64-unknown-openbsd4.6/lib/
-isystem
/home/iulius/autobuild/bin/gcc-core-4.6.1/sparc64-unknown-openbsd4.6/include
-isystem
/home/iulius/autobuild/bin/gcc-core-4.6.1/sparc64-unknown-openbsd4.6/sys-include
   -c -g -O2  conftest.c >&5
/home/iulius/autobuild/src/gcc-core-4.6.1/host-sparc64-unknown-openbsd4.6/gcc/cc1:/home/iulius/autobuild/src/gcc-core-4.6
.1/host-sparc64-unknown-openbsd4.6/gcc/cc1: undefined symbol ''
lazy binding failed!
cc1: internal compiler error: Segmentation fault
Please submit a full bu