Re: [PATCH] configure: add --disable-fix-includes
On 5/2/22 01:22, Martin Liška wrote: On 2/4/22 14:30, Jakub Jelinek via Gcc-patches wrote: We don't ship any include-fixed headers in Fedora/RHEL. Removing include-fixed from an installed folder, I see: make[2]: Entering directory '/home/marxin/Programming/postgres/src/common' gcc -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Werror=vla -Wendif-labels -Wmissing-format-attribute -Wimplicit-fallthrough=3 -Wcast-function-type -Wformat-security -fno-strict-aliasing -fwrapv -fexcess-precision=standard -Wno-format-truncation -Wno-stringop-truncation -O3 -march=native -flto=auto -DFRONTEND -I. -I../../src/common -I../../src/include -D_GNU_SOURCE -DVAL_CC="\"gcc\"" -DVAL_CPPFLAGS="\"-D_GNU_SOURCE\"" -DVAL_CFLAGS="\"-Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Werror=vla -Wendif-labels -Wmissing-format-attribute -Wimplicit-fallthrough=3 -Wcast-function-type -Wformat-security -fno-strict-aliasing -fwrapv -fexcess-precision=standard -Wno-format-truncation -Wno-stringop-truncation -O3 -march=native -flto=auto\"" -DVAL_CFLAGS_SL="\"-fPIC\"" -DVAL_LDFLAGS="\"-O3 -march=native -flto=auto -Wl,--as-needed -Wl,-rpath,'/usr/local/pgsql/lib64',--enable-new-dtags\"" -DVAL_LDFLAGS_EX="\"\"" -DVAL_LDFLAGS_SL="\"\"" -DVAL_LIBS="\"-lpgcommon -lpgport -lz -lreadline -lm \"" -c -o pg_lzcompress.o pg_lzcompress.c In file included from pg_lzcompress.c:186: /usr/include/limits.h:124:26: error: no include path in which to search for limits.h 124 | # include_next | ^ pg_lzcompress.c:226:9: error: ‘INT_MAX’ undeclared here (not in a function) 226 | INT_MAX, /* No upper limit on what we'll try to | ^~~ pg_lzcompress.c:189:1: note: ‘INT_MAX’ is defined in header ‘’; did you forget to ‘#include ’? 188 | #include "common/pg_lzcompress.h" +++ |+#include How do you solve this in Fedora/RHEL? The Fedora gcc.spec file has this: mv $FULLPATH/include-fixed/syslimits.h $FULLPATH/include/syslimits.h mv $FULLPATH/include-fixed/limits.h $FULLPATH/include/limits.h My understanding are these are not real fixinclude processed headers. Allan
[PATCH] testsuite/70230 - fix failures with default SSP
Configuring with --enable-default-ssp triggers various testsuite
failures. These contain asm statements that are not compatible with
-fstack-protector. Adding -fno-stack-protector to dg-options to
work around this issue.
Tested on x86_64-linux.
2022-01-26 Allan McRae
PR testsuite/70230
* gcc.dg/asan/use-after-scope-4.c (dg-options): Add
-fno-stack-protector.
* gcc.dg/stack-usage-1.c: Likewise
* gcc.dg/superblock.c: Likewise
* gcc.target/i386/avx-vzeroupper-17.c: Likewise
* gcc.target/i386/cleanup-1.c: Likewise
* gcc.target/i386/cleanup-2.c: Likewise
* gcc.target/i386/interrupt-redzone-1.c: Likewise
* gcc.target/i386/interrupt-redzone-2.c: Likewise
* gcc.target/i386/pr79793-1.c: Likewise
* gcc.target/i386/pr79793-2.c: Likewise
* gcc.target/i386/shrink_wrap_1.c: Likewise
* gcc.target/i386/stack-check-11.c: Likewise
* gcc.target/i386/stack-check-18.c: Likewise
* gcc.target/i386/stack-check-19.c: Likewise
* gcc.target/i386/stackalign/pr88483-1.c: Likewise
* gcc.target/i386/stackalign/pr88483-2.c: Likewise
* gcc.target/i386/sw-1.c: Likewise
---
gcc/testsuite/gcc.dg/asan/use-after-scope-4.c| 1 +
gcc/testsuite/gcc.dg/stack-usage-1.c | 2 +-
gcc/testsuite/gcc.dg/superblock.c| 2 +-
gcc/testsuite/gcc.target/i386/avx-vzeroupper-17.c| 2 +-
gcc/testsuite/gcc.target/i386/cleanup-1.c| 2 +-
gcc/testsuite/gcc.target/i386/cleanup-2.c| 2 +-
gcc/testsuite/gcc.target/i386/interrupt-redzone-1.c | 2 +-
gcc/testsuite/gcc.target/i386/interrupt-redzone-2.c | 2 +-
gcc/testsuite/gcc.target/i386/pr79793-1.c| 2 +-
gcc/testsuite/gcc.target/i386/pr79793-2.c| 2 +-
gcc/testsuite/gcc.target/i386/shrink_wrap_1.c| 2 +-
gcc/testsuite/gcc.target/i386/stack-check-11.c | 2 +-
gcc/testsuite/gcc.target/i386/stack-check-18.c | 2 +-
gcc/testsuite/gcc.target/i386/stack-check-19.c | 2 +-
gcc/testsuite/gcc.target/i386/stackalign/pr88483-1.c | 2 +-
gcc/testsuite/gcc.target/i386/stackalign/pr88483-2.c | 2 +-
gcc/testsuite/gcc.target/i386/sw-1.c | 2 +-
17 files changed, 17 insertions(+), 16 deletions(-)
diff --git a/gcc/testsuite/gcc.dg/asan/use-after-scope-4.c
b/gcc/testsuite/gcc.dg/asan/use-after-scope-4.c
index 44dc79535d2..e1486e75045 100644
--- a/gcc/testsuite/gcc.dg/asan/use-after-scope-4.c
+++ b/gcc/testsuite/gcc.dg/asan/use-after-scope-4.c
@@ -1,4 +1,5 @@
// { dg-do run }
+/* { dg-options "-fno-stack-protector" } */
#define FN(NAME) \
NAME (void) \
diff --git a/gcc/testsuite/gcc.dg/stack-usage-1.c
b/gcc/testsuite/gcc.dg/stack-usage-1.c
index 93cfe7c0163..1d7d1fee435 100644
--- a/gcc/testsuite/gcc.dg/stack-usage-1.c
+++ b/gcc/testsuite/gcc.dg/stack-usage-1.c
@@ -1,5 +1,5 @@
/* { dg-do compile } */
-/* { dg-options "-fstack-usage" } */
+/* { dg-options "-fstack-usage -fno-stack-protector" } */
/* nvptx doesn't have a reg allocator, and hence no stack usage data. */
/* { dg-skip-if "" { nvptx-*-* } } */
diff --git a/gcc/testsuite/gcc.dg/superblock.c
b/gcc/testsuite/gcc.dg/superblock.c
index 2b2fa9e154f..6b4419adaf5 100644
--- a/gcc/testsuite/gcc.dg/superblock.c
+++ b/gcc/testsuite/gcc.dg/superblock.c
@@ -1,5 +1,5 @@
/* { dg-do compile } */
-/* { dg-options "-O2 -fno-asynchronous-unwind-tables -fsched2-use-superblocks
-fdump-rtl-sched2 -fdump-rtl-bbro" } */
+/* { dg-options "-O2 -fno-asynchronous-unwind-tables -fsched2-use-superblocks
-fdump-rtl-sched2 -fdump-rtl-bbro -fno-stack-protector" } */
/* { dg-require-effective-target scheduling } */
typedef int aligned __attribute__ ((aligned (64)));
diff --git a/gcc/testsuite/gcc.target/i386/avx-vzeroupper-17.c
b/gcc/testsuite/gcc.target/i386/avx-vzeroupper-17.c
index 6dc0dc05321..d677e6f10e0 100644
--- a/gcc/testsuite/gcc.target/i386/avx-vzeroupper-17.c
+++ b/gcc/testsuite/gcc.target/i386/avx-vzeroupper-17.c
@@ -1,5 +1,5 @@
/* { dg-do compile { target lp64 } } */
-/* { dg-options "-O2 -mavx -mabi=ms -dp" } */
+/* { dg-options "-O2 -mavx -mabi=ms -dp -fno-stack-protector" } */
typedef float __m256 __attribute__ ((__vector_size__ (32), __may_alias__));
diff --git a/gcc/testsuite/gcc.target/i386/cleanup-1.c
b/gcc/testsuite/gcc.target/i386/cleanup-1.c
index dcfcc4edb5f..6e7544c6b7a 100644
--- a/gcc/testsuite/gcc.target/i386/cleanup-1.c
+++ b/gcc/testsuite/gcc.target/i386/cleanup-1.c
@@ -1,5 +1,5 @@
/* { dg-do run { target *-*-linux* *-*-gnu* } } */
-/* { dg-options "-fexceptions -fnon-call-exceptions
-fasynchronous-unwind-tables -O2" } */
+/* { dg-options "-fexceptions -fnon-call-exceptions
-fasynchronous-unwind-tables -O2 -fno-stack-protector" } */
/* Test complex CFA value expressions. */
#include
diff --git a/gcc/testsuite/gcc.target/i386/cleanup-2.c
b
Re: [PING][PATCH][1-3] New configure options that make the compiler use -fPIE and -pie as default option
On 31/12/14 07:23, Magnus Granberg wrote: fredag 14 november 2014 23.31.48 skrev Magnus Granberg: måndag 10 november 2014 21.26.39 skrev Magnus Granberg: Rainer Thanks Rainer for the nits and comments. Have updated the patches and Changelogs. But i still use PIE_DRIVER_SELF_SPECS, do you have a ide where move it so i don't need to duplicate that stuff or how to do it? Magnus G 2014-11-10 Magnus Granberg zo...@gentoo.org /gcc * config/gnu-user.h (PIE_DRIVER_SELF_SPECS) and (GNU_DRIVER_SELF_SPECS): Define. * config/i386/gnu-user-common.h (DRIVER_SELF_SPECS): Define * configure.ac: Add new option. * configure, config.in: Rebuild. * Makefile.in (ALL_CFLAGS) and (ALL_CXXFLAGS): Disable PIE. * doc/install.texi: New configure option. * doc/invoke.texi: Add note to PIE. * doc/sourcebuild.texi: New effective target. gcc/testsuite * gcc/default-pie.c: New test * gcc.dg/tree-ssa/ssa-store-ccp-3.c: Skip if default_pie * g++.dg/other/anon5.C: Skip if default_pie * lib/target-supports.exp (check_effective_target_default_pie): New proc. /libgcc * Makefile.in (CRTSTUFF_CFLAGS): Disable PIE. Can this be included for GCC 5 ? /Magnus G. One more ping on this. The patches where sent before stage 1 closed but i did't get any feed back from it Have updete the patchses for gcc 5.0 20141228 snapshot. Bootstrapped and tested on x86_64-unknown-linux-gnu (Gentoo) /Magnus I'm giving this a further ping as my distribution has interest in these patches. Thanks! 2014-12-30 Magnus Granberg zo...@gentoo.org /gcc * config/gnu-user.h (PIE_DRIVER_SELF_SPECS): Define. * config/i386/gnu-user-common.h (DRIVER_SELF_SPECS): Define and add PIE_DRIVER_SELF_SPECS. * configure.ac: Add new option. * configure, config.in: Rebuild. * Makefile.in (ALL_CFLAGS) and (ALL_CXXFLAGS): Disable PIE. * doc/install.texi: New configure option. * doc/invoke.texi: Add note to PIE. * doc/sourcebuild.texi: New effective target. gcc/testsuite * gcc/default-pie.c: New test * gcc.dg/tree-ssa/ssa-store-ccp-3.c: Skip if default_pie * g++.dg/other/anon5.C: Skip if default_pie * lib/target-supports.exp (check_effective_target_default_pie): New proc. /libgcc * Makefile.in (CRTSTUFF_CFLAGS): Disable PIE.
Re: MELT plugin 0.8rc4 for 4.6
On 11/07/11 03:15, Basile Starynkevitch wrote: On Sun, 10 Jul 2011 19:00:14 +0200 Basile Starynkevitchbas...@starynkevitch.net wrote: For your information, I corrected that bug (not only made the workaround) on MELT svn rev. 176125. So I think that the MELT plugin 0.8 final (which I will probably release in a couple of days) will have that bug corrected. I just released MELT plugin 0.8rc4 with that change. See http://gcc-melt.org/ and download http://gcc-melt.org/melt-0.8rc4-plugin-for-gcc-4.6.tgz When I have a successful build report, I will release it as MELT 0.8 plugin. Same news (w.r.t to MELT 0.7) as in http://gcc.gnu.org/ml/gcc/2011-07/msg00126.html I can give a successful build report for melt-0.8rc4 on i686-pc-linux-gnu using make all. Some issues I noticed with make install make DESTDIR=/tmp/melt install ... install: target `/tmp/melt//usr/lib/gcc/i686-pc-linux-gnu/4.6.1/plugin/include/' is not a directory: No such file or directory This needs added to install-melt-includes: $(mkinstalldirs) $(DESTDIR)/$(MELTGCC_PLUGIN_DIR)/include/ Then I run into an error in install-melt-modules: install: cannot stat `melt-modules/*.so': No such file or directory In that directory I have three subdirectories containing built modules. I guess one of them is supposed to be used. All other install targets work fine. Allan
Re: announce: MELT plugin 0.8rc2 for 4.6
On 08/07/11 18:06, Basile Starynkevitch wrote: Hello All, It is my pleasure to announce the 2nd release candidate of MELT plugin version 0.8 for GCC 4.6 You can download it from http://gcc-melt.org/ gnuzipped tar http://gcc-melt.org/melt-0.8rc2-plugin-for-gcc-4.6.tgz of md5sum 880db34a1d76a27f51ba4d594e725519 I get an ICE after stage zero: build-melt-plugin: Did MELT stage zero successfully build-melt-plugin: Starting MELT first stage build-melt-plugin: making MELT using /home/allan/Desktop/melt-0.8rc2-plugin-for-gcc-4.6/melt-build.mk warmelt1 make: Entering directory `/home/allan/Desktop/melt-0.8rc2-plugin-for-gcc-4.6' if [ -d melt-stage1 ]; then true; else mkdir melt-stage1; fi cd melt-stage0-dynamic/ ; rm -f warmelt-first-0.so; ln -s warmelt-first-0.d.so warmelt-first-0.so cd melt-stage0-dynamic/ ; rm -f warmelt-base-0.so; ln -s warmelt-base-0.d.so warmelt-base-0.so cd melt-stage0-dynamic/ ; rm -f warmelt-debug-0.so; ln -s warmelt-debug-0.d.so warmelt-debug-0.so cd melt-stage0-dynamic/ ; rm -f warmelt-macro-0.so; ln -s warmelt-macro-0.d.so warmelt-macro-0.so cd melt-stage0-dynamic/ ; rm -f warmelt-normal-0.so; ln -s warmelt-normal-0.d.so warmelt-normal-0.so cd melt-stage0-dynamic/ ; rm -f warmelt-normatch-0.so; ln -s warmelt-normatch-0.d.so warmelt-normatch-0.so cd melt-stage0-dynamic/ ; rm -f warmelt-genobj-0.so; ln -s warmelt-genobj-0.d.so warmelt-genobj-0.so cd melt-stage0-dynamic/ ; rm -f warmelt-outobj-0.so; ln -s warmelt-outobj-0.d.so warmelt-outobj-0.so gcc -fplugin=./melt.so -c -o /dev/null -Wno-shadow -fplugin-arg-melt-mode=translateinit -fplugin-arg-melt-module-makefile=/home/allan/Desktop/melt-0.8rc2-plugin-for-gcc-4.6/melt-module.mk -fplugin-arg-melt-module-make-command=/usr/bin/make -fplugin-arg-melt-tempdir=. -fplugin-arg-melt-bootstrapping -fplugin-arg-melt-init=\ warmelt-first-0:\ warmelt-base-0:\ warmelt-debug-0:\ warmelt-macro-0:\ warmelt-normal-0:\ warmelt-normatch-0:\ warmelt-genobj-0:\ warmelt-outobj-0 \ -fplugin-arg-melt-arg=/home/allan/Desktop/melt-0.8rc2-plugin-for-gcc-4.6/melt/warmelt-first.melt -frandom-seed=c763ca1e2b1d2b340ebd439b \ -fplugin-arg-melt-module-path=melt-stage1:melt-stage0-dynamic:.:. \ -fplugin-arg-melt-source-path=melt-stage1:melt-stage0-dynamic:.:/home/allan/Desktop/melt-0.8rc2-plugin-for-gcc-4.6/melt:/home/allan/Desktop/melt-0.8rc2-plugin-for-gcc-4.6/melt/generated:/usr/lib/gcc/i686-pc-linux-gnu/4.6.1/plugin/melt-source \ -fplugin-arg-melt-output=melt-stage1/warmelt-first-1.c empty-file-for-melt.c cc1: note: MELT is bootstrapping so ignore builtin source directory /usr/lib/gcc/i686-pc-linux-gnu/4.6.1/plugin/melt-source and module directory /usr/lib/gcc/i686-pc-linux-gnu/4.6.1/plugin/libexec/melt-modules *** WARNING *** there are active plugins, do not report this as a bug unless you can reproduce it without enabling any plugins. Event| Plugins PLUGIN_FINISH_UNIT | melt PLUGIN_FINISH| melt PLUGIN_GGC_START | melt PLUGIN_GGC_MARKING | melt PLUGIN_ATTRIBUTES| melt PLUGIN_START_UNIT| melt PLUGIN_PRAGMAS | melt cc1: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See https://bugs.archlinux.org/ for instructions. make: *** [melt-stage1/warmelt-first-1.c] Error 1 make: Leaving directory `/home/allan/Desktop/melt-0.8rc2-plugin-for-gcc-4.6' build-melt-plugin error: doing melt make warmelt1 failed gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-pc-linux-gnu/4.6.1/lto-wrapper Target: i686-pc-linux-gnu Configured with: /build/src/gcc-4.6.1/configure --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=posix --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu --enable-gnu-unique-object --enable-linker-build-id --with-ppl --enable-cloog-backend=isl --enable-lto --enable-gold --enable-ld=default --enable-plugin --with-plugin-ld=ld.gold --disable-multilib --disable-libstdcxx-pch --enable-checking=release Thread model: posix gcc version 4.6.1 (GCC) What further information do you require for this? Allan
Re: announce: MELT plugin 0.8rc2 for 4.6
On 08/07/11 19:15, Basile Starynkevitch wrote: On Fri, Jul 08, 2011 at 06:41:30PM +1000, Allan McRae wrote: empty-file-for-melt.c cc1: note: MELT is bootstrapping so ignore builtin source directory /usr/lib/gcc/i686-pc-linux-gnu/4.6.1/plugin/melt-source and module directory /usr/lib/gcc/i686-pc-linux-gnu/4.6.1/plugin/libexec/melt-modules *** WARNING *** there are active plugins, do not report this as a bug unless you can reproduce it without enabling any plugins. Event| Plugins PLUGIN_FINISH_UNIT | melt PLUGIN_FINISH| melt PLUGIN_GGC_START | melt PLUGIN_GGC_MARKING | melt PLUGIN_ATTRIBUTES| melt PLUGIN_START_UNIT| melt PLUGIN_PRAGMAS | melt cc1: internal compiler error: Segmentation fault Please submit a full bug report, Did you install a previous release of MELT plugin (e.g. 0.8rc1 or 0.7)? If you did, you have to remove it entirely (eg remove all files named *melt*)? I have no previous MELT plugins installed. What further information do you require for this? Perhaps a gdb backtrace of the crash? Maybe not that helpful given things have been stripped... I can rebuild without stripping if helpful. #0 0xf7fe6941 in _dl_lookup_symbol_x () from /lib/ld-linux.so.2 #1 0xf788ed60 in ?? () from /lib/libc.so.6 #2 0xf788f1e7 in _dl_sym () from /lib/libc.so.6 #3 0xf7902d66 in ?? () from /lib/libdl.so.2 #4 0xf7feb66f in _dl_catch_error () from /lib/ld-linux.so.2 #5 0xf790333a in ?? () from /lib/libdl.so.2 #6 0xf7902de4 in dlsym () from /lib/libdl.so.2 #7 0xf71a7605 in melt_dlsym_all () from ./melt.so #8 0xf71a7666 in melt_dynobjstruct_fieldoffset_at () from ./melt.so #9 0xf708ad3c in warmelt_first_initialmeltchunk_19 () from melt-stage0-dynamic/warmelt-first-0.so #10 0xf70fa485 in start_module_melt () from melt-stage0-dynamic/warmelt-first-0.so #11 0xf71b9b3b in meltgc_make_load_melt_module () from ./melt.so #12 0xf71c3bc3 in plugin_init () from ./melt.so #13 0x082d5565 in ?? () #14 0x087663c5 in htab_traverse_noresize () #15 0x082d5ebd in initialize_plugins () #16 0x08364c2e in toplev_main () #17 0x080d645b in main () Note that this only happens for me on i686. I have just set off a build on my x86_64 system (toolchain build with exactly the same configuration) and I do not run into this issue. Allan
Re: announce: MELT plugin 0.8rc2 for 4.6
On 09/07/11 01:43, Basile Starynkevitch wrote: On Fri, 08 Jul 2011 19:50:11 +1000 Allan McRaeal...@archlinux.org wrote: On 08/07/11 19:15, Basile Starynkevitch wrote: On Fri, Jul 08, 2011 at 06:41:30PM +1000, Allan McRae wrote: empty-file-for-melt.c cc1: note: MELT is bootstrapping so ignore builtin source directory /usr/lib/gcc/i686-pc-linux-gnu/4.6.1/plugin/melt-source and module directory /usr/lib/gcc/i686-pc-linux-gnu/4.6.1/plugin/libexec/melt-modules *** WARNING *** there are active plugins, do not report this as a bug unless you can reproduce it without enabling any plugins. Event| Plugins PLUGIN_FINISH_UNIT | melt PLUGIN_FINISH| melt PLUGIN_GGC_START | melt PLUGIN_GGC_MARKING | melt PLUGIN_ATTRIBUTES| melt PLUGIN_START_UNIT| melt PLUGIN_PRAGMAS | melt cc1: internal compiler error: Segmentation fault Please submit a full bug report, Did you install a previous release of MELT plugin (e.g. 0.8rc1 or 0.7)? If you did, you have to remove it entirely (eg remove all files named *melt*)? Alexandre Lissy discovered that by replacing, in file melt-0.8rc2-plugin-for-gcc-4.6/melt-build.mk line 420, MELT_STAGE_ZERO?= melt-stage0-dynamic with MELT_STAGE_ZERO = melt-stage0-static the bug disappears. Allan, could you confirm that it is the case for you also? Thanks! I can confirm the build completes with that change. Allan
Re: Snapshot tarballs for 4.7-20110528
On 02/06/11 23:51, bd satish wrote: Hi, All these days there used to be different tarballs like gcc-core-*.tar.bz2, gcc-fortran-*.tar.bz2, etc. in the snapshot directory ftp://gcc.gnu.org/pub/gcc/snapshots/LATEST-4.7. But now I see only one combined tarball (starting with 4.7-20110528). I liked separate tarballs on a per-language basis (g++, fortran, etc.). Could somebody point me to the reasons for this change ? I couldn't find any announcement regarding this change either. I noticed that this has also happened with gcc-4.5-20110602. Is this due to some failure or is this change deliberate? Allan
Re: Snapshot tarballs for 4.7-20110528
On 03/06/11 15:39, Allan McRae wrote: On 02/06/11 23:51, bd satish wrote: Hi, All these days there used to be different tarballs like gcc-core-*.tar.bz2, gcc-fortran-*.tar.bz2, etc. in the snapshot directory ftp://gcc.gnu.org/pub/gcc/snapshots/LATEST-4.7. But now I see only one combined tarball (starting with 4.7-20110528). I liked separate tarballs on a per-language basis (g++, fortran, etc.). Could somebody point me to the reasons for this change ? I couldn't find any announcement regarding this change either. I noticed that this has also happened with gcc-4.5-20110602. Is this due to some failure or is this change deliberate? To clarify further: gcc-4.7-20110521 generated all the separate tarballs per language gcc-4.3-20110522 (and all snapshots thereafter) only generated a single tarball Allan
Re: glibc 2.13-4 causing kdesktop.kcrash (x86_64 only); 2.13-3 OK - right place to report?
On 23/02/11 05:25, David C. Rankin wrote: (1) if this is the right place for the glibc issue; and No. This list is for the development of gcc. (2) if you think it is something that should be filed or whether the error points to a packaging problem or a problem with the Trinity source. Given downgrading the distributions glibc package fixed the issue, the first point of call should be me on the Arch Linux bug tracker. Allan
Re: gmp 5.0.1 and gcc 4.5?
On 03/04/10 03:28, Roman Kononov wrote: On Mon, 29 Mar 2010 12:55:47 -0400 Jack Howarth howa...@bromo.med.uc.edu wrote: I've not seen any discussion of testing gcc trunk against the newer gmp 5.0 or 5.0.1 releases. Has anyone done significant testing with the newer gmp releases ... ? I use gcc 4.4.4 and 4.5.0 with gmp 5.0.1. I compile and use PostgreSQL and other stuff, and have not noticed any misbehavior related to gmp or mpfr. Although, I cannot say that I use gcc in a way that makes a lot of gmp or mpfr testing. The Arch Linux toolchain was built with gmp-5.0.1 about two weeks ago and all software linking to gmp-4 was rebuilt with gmp-5. We have seen no gmp-5 related issues so far. Allan
Re: [Cygwin] Failure in building current GCC snapshot
Angelo Graziosi wrote:
At least on Cygwin (1.7), the current GCC snapshot (20090917) fails to
build:
[...]
/tmp/build/./gcc/xgcc -B/tmp/build/./gcc/
-B/usr/local/gfortran/i686-pc-cygwin/bin/
-B/usr/local/gfortran/i686-pc-cygwin/lib/ -isystem
/usr/local/gfortran/i686-pc-cygwin/include -isystem
/usr/local/gfortran/i686-pc-cygwin/sys-include-g -O2 -O2
-I/tmp/gcc-4.5-20090917/gcc/../winsup/w32api/include
-I/tmp/gcc-4.5-20090917/gcc/../winsup/include
-I/tmp/gcc-4.5-20090917/gcc/../winsup/cygwin/include -g -O2 -DIN_GCC
-W -Wall -Wwrite-strings -Wcast-qual -Wstrict-prototypes
-Wmissing-prototypes -Wold-style-definition -isystem ./include -g
-DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -I. -I.
-I../.././gcc -I/tmp/gcc-4.5-20090917/libgcc
-I/tmp/gcc-4.5-20090917/libgcc/. -I/tmp/gcc-4.5-20090917/libgcc/../gcc
-I/tmp/gcc-4.5-20090917/libgcc/../include
-I/tmp/gcc-4.5-20090917/libgcc/../libdecnumber/dpd
-I/tmp/gcc-4.5-20090917/libgcc/../libdecnumber -DHAVE_CC_TLS -o
_powitf2.o -MT _powitf2.o -MD -MP -MF _powitf2.dep -DL_powitf2 -c
/tmp/gcc-4.5-20090917/libgcc/../gcc/libgcc2.c \
/tmp/gcc-4.5-20090917/libgcc/../gcc/libgcc2.c: In function '__powisf2':
/tmp/gcc-4.5-20090917/libgcc/../gcc/libgcc2.c:1739:1: internal
compiler error: in convert_regs_1, at reg-stack.c:3052
Please submit a full bug report,
with preprocessed source if appropriate.
See http://gcc.gnu.org/bugs.html for instructions.
make[3]: *** [_powisf2.o] Error 1
make[3]: *** Waiting for unfinished jobs
/tmp/gcc-4.5-20090917/libgcc/../gcc/libgcc2.c: In function '__powidf2':
/tmp/gcc-4.5-20090917/libgcc/../gcc/libgcc2.c:1739:1: internal
compiler error: in convert_regs_1, at reg-stack.c:3052
Please submit a full bug report,
with preprocessed source if appropriate.
See http://gcc.gnu.org/bugs.html for instructions.
make[3]: *** [_powidf2.o] Error 1
/tmp/gcc-4.5-20090917/libgcc/../gcc/libgcc2.c: In function '__powixf2':
/tmp/gcc-4.5-20090917/libgcc/../gcc/libgcc2.c:1739:1: internal
compiler error: in convert_regs_1, at reg-stack.c:3052
Please submit a full bug report,
with preprocessed source if appropriate.
See http://gcc.gnu.org/bugs.html for instructions.
make[3]: *** [_powixf2.o] Error 1
make[3]: Leaving directory `/tmp/build/i686-pc-cygwin/libgcc'
make[2]: *** [all-stage2-target-libgcc] Error 2
make[2]: Leaving directory `/tmp/build'
make[1]: *** [stage2-bubble] Error 2
make[1]: Leaving directory `/tmp/build'
make: *** [all] Error 2
---
I have configured with:
-
${source_dir}/configure --prefix=${prefix_dir} \
--exec-prefix=${eprefix_dir} \
--sysconfdir=${sysconf_dir} \
--libdir=${lib_dir} \
--libexecdir=${libexec_dir} \
--mandir=${man_dir} \
--infodir=${info_dir} \
--program-suffix=${suffix} \
--enable-bootstrap \
--enable-checking=release \
--enable-decimal-float \
--enable-languages=c,c++,fortran \
--enable-libgomp \
--enable-libssp \
--enable-nls \
--enable-threads=posix \
--enable-version-specific-runtime-libs \
--disable-libmudflap \
--disable-shared \
--disable-sjlj-exceptions \
--disable-win32-registry \
--with-arch=i686 \
--with-dwarf2 \
--with-system-zlib \
--with-tune=generic \
--without-included-gettext \
--without-x
-
The previous snapshot (20090910) builds fine, with the same methods.
Seems to be the same as http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41395
Allan
Re: Using MPC Library with GCC
Kaveh R. GHAZI wrote:
On Wed, 13 May 2009, Mark Mitchell wrote:
Kaveh R. GHAZI wrote:
1. Consider MPC as an optional library now, install all the code and make
it hard-required only when all the complex math functions are made
available in a future released version of the library or sometime in
stage3, whichever is first.
I think this is the best option.
Please make sure to open a P1 PR for 4.5.0 indicating that we should
throw the hard-requirement switch.
The last patch to enable use of MPC in GCC was reviewed today and
installed. I'm sure other updates will come, but the base functionality
is now there.
I've opened PR 40302 as you requested (and assigned myself).
I have noticed that mpc is not automatically detected even when
installed in the standard library path (with gcc-4.5-20090604). This
means that building with mpc always requires using the
--with-mpc-lib=/usr/lib flag.
This is fixed by adjusting configure{.ac} to have:
mpclibs=-lmpc
Allan
