public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "baker at usgs dot gov" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/54584] m68k-uclinux error: Link tests are not allowed after GCC_NO_EXECUTABLES Date: Sat, 15 Sep 2012 00:39:00 -0000 [thread overview] Message-ID: <bug-54584-4-ItLfpIAOYy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54584-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54584 --- Comment #1 from Larry Baker <baker at usgs dot gov> 2012-09-15 00:39:14 UTC --- I found that the -msep-data link would succeed if program section .tm_clone_table has a non-zero length. I changed __JCR_LIST__[] and __TMC_LIST__[] to __JCR_LIST__[1] and __TMC_LIST__[1], respectively, in gcc-4.7-20120908/libgcc/crtstuff.c. The program sections in the original crtbegin.o have 0 length for program section .tm_clone_table: # freescale-coldfire-2011.09/bin/m68k-uclinux-objdump -h cross-gcc-4.7-20120908/gcc/msep-data/crtbegin.o cross-gcc-4.7-20120908/gcc/msep-data/crtbegin.o: file format elf32-m68k Sections: Idx Name Size VMA LMA File off Algn 0 .text 00000136 00000000 00000000 00000034 2**2 CONTENTS, ALLOC, LOAD, RELOC, READONLY, CODE 1 .data 00000004 00000000 00000000 0000016c 2**2 CONTENTS, ALLOC, LOAD, DATA 2 .bss 0000001e 00000000 00000000 00000170 2**2 ALLOC 3 .ctors 00000004 00000000 00000000 00000170 2**2 CONTENTS, ALLOC, LOAD, DATA 4 .dtors 00000004 00000000 00000000 00000174 2**2 CONTENTS, ALLOC, LOAD, DATA 5 .eh_frame 00000000 00000000 00000000 00000178 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA 6 .jcr 00000000 00000000 00000000 00000178 2**2 CONTENTS, ALLOC, LOAD, DATA 7 .tm_clone_table 00000000 00000000 00000000 00000178 2**2 CONTENTS, ALLOC, LOAD, DATA 8 .fini 00000006 00000000 00000000 00000178 2**0 CONTENTS, ALLOC, LOAD, RELOC, READONLY, CODE 9 .init 00000006 00000000 00000000 0000017e 2**0 CONTENTS, ALLOC, LOAD, RELOC, READONLY, CODE 10 .comment 00000028 00000000 00000000 00000184 2**0 CONTENTS, READONLY 11 .note.GNU-stack 00000000 00000000 00000000 000001ac 2**0 CONTENTS, READONLY The new one has length 4: # freescale-coldfire-2011.09/bin/m68k-uclinux-objdump -h cross-gcc-4.7-20120908/gcc/msep-data/crtbegin.o cross-gcc-4.7-20120908/gcc/msep-data/crtbegin.o: file format elf32-m68k Sections: Idx Name Size VMA LMA File off Algn 0 .text 00000136 00000000 00000000 00000034 2**2 CONTENTS, ALLOC, LOAD, RELOC, READONLY, CODE 1 .data 00000004 00000000 00000000 0000016c 2**2 CONTENTS, ALLOC, LOAD, DATA 2 .bss 0000001e 00000000 00000000 00000170 2**2 ALLOC 3 .ctors 00000004 00000000 00000000 00000170 2**2 CONTENTS, ALLOC, LOAD, DATA 4 .dtors 00000004 00000000 00000000 00000174 2**2 CONTENTS, ALLOC, LOAD, DATA 5 .eh_frame 00000000 00000000 00000000 00000178 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA 6 .jcr 00000004 00000000 00000000 00000178 2**2 CONTENTS, ALLOC, LOAD, DATA 7 .tm_clone_table 00000004 00000000 00000000 0000017c 2**2 CONTENTS, ALLOC, LOAD, DATA 8 .fini 00000006 00000000 00000000 00000180 2**0 CONTENTS, ALLOC, LOAD, RELOC, READONLY, CODE 9 .init 00000006 00000000 00000000 00000186 2**0 CONTENTS, ALLOC, LOAD, RELOC, READONLY, CODE 10 .comment 00000028 00000000 00000000 0000018c 2**0 CONTENTS, READONLY 11 .note.GNU-stack 00000000 00000000 00000000 000001b4 2**0 CONTENTS, READONLY I do not know if this results in a correctly allocated or populated .tm_clone_table. All I know is that the zero length allocation caused the link failure. Is this due to the ALLOC attribute with 0 length? Is this a consequence of __attribute__((used))?
next prev parent reply other threads:[~2012-09-15 0:39 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-14 20:44 [Bug target/54584] New: " baker at usgs dot gov 2012-09-15 0:39 ` baker at usgs dot gov [this message] 2012-09-18 2:45 ` [Bug target/54584] " baker at usgs dot gov 2012-09-18 21:43 ` baker at usgs dot gov 2012-09-18 21:53 ` baker at usgs dot gov 2012-09-18 23:30 ` hp at gcc dot gnu.org 2012-09-19 0:05 ` baker at usgs dot gov 2012-09-19 0:15 ` baker at usgs dot gov
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-54584-4-ItLfpIAOYy@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: 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).