public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hp at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/37170] [4.4 Regression]: gcc.dg/weak/weak-1.c Date: Sun, 31 Aug 2008 20:34:00 -0000 [thread overview] Message-ID: <20080831203328.25873.qmail@sourceware.org> (raw) In-Reply-To: <bug-37170-507@http.gcc.gnu.org/bugzilla/> ------- Comment #75 from hp at gcc dot gnu dot org 2008-08-31 20:33 ------- (In reply to comment #74) > > Patch, take 6. > > This one is a significant improvement. In the C testsuite, I'm > seeing a few failures like this one: > > Executing on host: /test/gnu/gcc/objdir/gcc/xgcc -B/test/gnu/gcc/objdir/gcc/ > /te > st/gnu/gcc/gcc/gcc/testsuite/gcc.dg/struct/w_prof_global_array.c -O3 > -fwhole- > program -combine -fipa-type-escape -fprofile-generate -lm -o > /test/gnu/gcc/ob > jdir/gcc/testsuite/gcc/w_prof_global_array.x01 (timeout = 300) > /usr/ccs/bin/ld: Unsatisfied symbols: > _GLOBAL__FI_w_prof_global_array_x01 (first referenced in +init option) > (code) > _GLOBAL__FD_w_prof_global_array_x01 (first referenced in +fini option) > (code) > collect2: ld returned 1 exit status Is this really a regression? What unpatched revision did you use as a baseline? When I compile that testcase, edited because of the stdlib include as follows: --- w_prof_global_array.c 2008-01-03 16:12:42.000000000 +0100 +++ /home/hp/wp.c 2008-08-31 21:09:44.000000000 +0200 @@ -1,4 +1,4 @@ -#include <stdlib.h> +extern void abort(void); typedef struct { int a; I don't see a difference unpatched/patched at revision 139233 in the generated assembly code, compiling with: ./xgcc -B./ -S ~/wp.c -o wp.s -O3 -fwhole-program -combine -fipa-type-escape -fprofile-generate (and no, adding "__attribute__ ((__noreturn__))" still makes no difference.) > Executing on host: /test/gnu/gcc/objdir/gcc/testsuite/g++/../../g++ > -B/test/gnu/ > gcc/objdir/gcc/testsuite/g++/../../ > /test/gnu/gcc/gcc/gcc/testsuite/g++.old-deja > /g++.other/static14.C -nostdinc++ > -I/test/gnu/gcc/objdir/hppa2.0w-hp-hpux11.11/ > libstdc++-v3/include/hppa2.0w-hp-hpux11.11 > -I/test/gnu/gcc/objdir/hppa2.0w-hp-hp > ux11.11/libstdc++-v3/include -I/test/gnu/gcc/gcc/libstdc++-v3/libsupc++ > -I/test/ > gnu/gcc/gcc/libstdc++-v3/include/backward > -I/test/gnu/gcc/gcc/libstdc++-v3/tests > uite/util -fmessage-length=0 -ansi -pedantic-errors -Wno-long-long > -L/test/ > gnu/gcc/objdir/hppa2.0w-hp-hpux11.11/./libstdc++-v3/src/.libs > -L/test/gnu/gcc/o > bjdir/hppa2.0w-hp-hpux11.11/./libstdc++-v3/src/.libs > -L/test/gnu/gcc/objdir/hppa > 2.0w-hp-hpux11.11/./libiberty -lm -o static14.exe (timeout = 300) > /usr/ccs/bin/ld: Unsatisfied symbols: > basic_string::~basic_string() (first referenced in /var/tmp//ccI3Feaf.o) > (code) > Side::name()::sname (first referenced in /var/tmp//ccI3Feaf.o) (data) > collect2: ld returned 1 exit status > compiler exited with status 1 No difference here either "-ansi -pedantic-errors -Wno-long-long". Weirdness: I see references in the generated code to basic_string::~basic_string() and Side::name()::sname, and that generated code isn't there for cris-elf or native. Ditto static20.C Maybe I'd see a difference if I force weak support? Let me check... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37170
next prev parent reply other threads:[~2008-08-31 20:34 UTC|newest] Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-08-20 0:47 [Bug middle-end/37170] New: " hp at gcc dot gnu dot org 2008-08-20 0:47 ` [Bug middle-end/37170] " hp at gcc dot gnu dot org 2008-08-20 15:32 ` hp at gcc dot gnu dot org 2008-08-21 0:27 ` eric dot weddington at atmel dot com 2008-08-21 0:34 ` hp at gcc dot gnu dot org 2008-08-21 9:17 ` dominiq at lps dot ens dot fr 2008-08-21 13:30 ` hp at gcc dot gnu dot org 2008-08-21 15:34 ` dominiq at lps dot ens dot fr 2008-08-21 17:08 ` eric dot weddington at atmel dot com 2008-08-21 17:14 ` eric dot weddington at atmel dot com 2008-08-21 19:05 ` eric dot weddington at atmel dot com 2008-08-21 19:07 ` dominiq at lps dot ens dot fr 2008-08-21 20:06 ` hp at gcc dot gnu dot org 2008-08-22 2:18 ` hp at gcc dot gnu dot org 2008-08-22 2:25 ` hp at gcc dot gnu dot org 2008-08-22 3:39 ` eric dot weddington at atmel dot com 2008-08-22 11:49 ` dominiq at lps dot ens dot fr 2008-08-22 11:53 ` dominiq at lps dot ens dot fr 2008-08-22 13:15 ` hp at gcc dot gnu dot org 2008-08-22 13:24 ` dominiq at lps dot ens dot fr 2008-08-22 13:46 ` eric dot weddington at atmel dot com 2008-08-22 14:16 ` rguenth at gcc dot gnu dot org 2008-08-22 14:20 ` hp at gcc dot gnu dot org 2008-08-22 14:52 ` eric dot weddington at atmel dot com 2008-08-22 14:53 ` eric dot weddington at atmel dot com 2008-08-22 14:55 ` dominiq at lps dot ens dot fr 2008-08-22 14:56 ` dominiq at lps dot ens dot fr 2008-08-22 15:27 ` hp at gcc dot gnu dot org 2008-08-22 17:10 ` dominiq at lps dot ens dot fr 2008-08-22 17:19 ` hp at gcc dot gnu dot org 2008-08-22 18:08 ` eric dot weddington at atmel dot com 2008-08-22 18:19 ` hp at gcc dot gnu dot org 2008-08-22 18:43 ` andreast at gcc dot gnu dot org 2008-08-23 8:18 ` andreast at gcc dot gnu dot org 2008-08-23 18:40 ` hp at gcc dot gnu dot org 2008-08-24 16:47 ` dominiq at lps dot ens dot fr 2008-08-24 16:51 ` dominiq at lps dot ens dot fr 2008-08-25 1:28 ` hp at gcc dot gnu dot org 2008-08-25 1:50 ` hp at gcc dot gnu dot org 2008-08-25 2:10 ` hp at gcc dot gnu dot org 2008-08-25 9:57 ` dominiq at lps dot ens dot fr 2008-08-25 11:45 ` dominiq at lps dot ens dot fr 2008-08-25 13:36 ` dominiq at lps dot ens dot fr 2008-08-25 15:14 ` eric dot weddington at atmel dot com 2008-08-25 16:52 ` eric dot weddington at atmel dot com 2008-08-25 17:11 ` dominiq at lps dot ens dot fr 2008-08-25 17:22 ` eric dot weddington at atmel dot com 2008-08-25 17:26 ` dominiq at lps dot ens dot fr 2008-08-25 17:59 ` hp at gcc dot gnu dot org 2008-08-25 18:14 ` dominiq at lps dot ens dot fr 2008-08-25 18:19 ` dominiq at lps dot ens dot fr 2008-08-25 18:37 ` hp at gcc dot gnu dot org 2008-08-25 18:59 ` pinskia at gcc dot gnu dot org 2008-08-25 19:17 ` hp at gcc dot gnu dot org 2008-08-25 20:25 ` dominiq at lps dot ens dot fr 2008-08-25 21:37 ` hp at gcc dot gnu dot org 2008-08-26 2:01 ` hp at gcc dot gnu dot org 2008-08-26 11:58 ` dominiq at lps dot ens dot fr 2008-08-27 14:53 ` hp at gcc dot gnu dot org 2008-08-27 15:24 ` dominiq at lps dot ens dot fr 2008-08-27 15:42 ` hp at gcc dot gnu dot org 2008-08-27 16:35 ` hp at gcc dot gnu dot org 2008-08-28 21:07 ` eric dot weddington at atmel dot com 2008-08-29 17:18 ` andreast at gcc dot gnu dot org 2008-08-29 20:52 ` hp at gcc dot gnu dot org 2008-08-29 22:41 ` dave at hiauly1 dot hia dot nrc dot ca 2008-08-30 0:41 ` hp at gcc dot gnu dot org 2008-08-30 1:07 ` hp at gcc dot gnu dot org 2008-08-30 1:09 ` hp at gcc dot gnu dot org 2008-08-30 1:20 ` dave at hiauly1 dot hia dot nrc dot ca 2008-08-30 2:49 ` dave at hiauly1 dot hia dot nrc dot ca 2008-08-30 3:21 ` hp at gcc dot gnu dot org 2008-08-30 3:39 ` hp at gcc dot gnu dot org 2008-08-30 6:28 ` hp at gcc dot gnu dot org 2008-08-30 18:20 ` dave at hiauly1 dot hia dot nrc dot ca 2008-08-30 18:46 ` hp at gcc dot gnu dot org 2008-08-31 3:21 ` dave at hiauly1 dot hia dot nrc dot ca 2008-08-31 20:34 ` hp at gcc dot gnu dot org [this message] 2008-08-31 21:32 ` dave at hiauly1 dot hia dot nrc dot ca 2008-08-31 22:53 ` hp at gcc dot gnu dot org 2008-09-01 1:43 ` hp at gcc dot gnu dot org 2008-09-02 10:20 ` hp at gcc dot gnu dot org 2008-09-02 14:07 ` dave at hiauly1 dot hia dot nrc dot ca 2008-09-09 20:23 ` jsm28 at gcc dot gnu dot org 2008-09-22 1:56 ` hp at gcc dot gnu dot org 2008-09-22 1:57 ` hp at gcc dot gnu dot org 2008-09-22 2:07 ` hp at gcc dot gnu dot org 2008-09-24 9:53 ` aldot at gcc dot gnu dot org 2008-11-03 13:15 ` [Bug target/37170] " jakub at gcc dot gnu dot org 2008-11-22 8:25 ` jakub at gcc dot gnu dot org 2008-11-22 8:28 ` jakub at gcc dot gnu dot org 2008-11-22 8:32 ` jakub at gcc dot gnu dot org 2008-12-10 8:49 ` ebotcazou 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=20080831203328.25873.qmail@sourceware.org \ --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: linkBe 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).