public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "liwei79 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/46125] New: -mcmodel=large doesn't work Date: Fri, 22 Oct 2010 01:53:00 -0000 [thread overview] Message-ID: <bug-46125-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46125 Summary: -mcmodel=large doesn't work Product: gcc Version: 4.5.1 Status: UNCONFIRMED Severity: critical Priority: P3 Component: other AssignedTo: unassigned@gcc.gnu.org ReportedBy: liwei79@gmail.com Hi, I am working on huge object files and I am glad to see that gcc supports -mcmodel=large now. However, my experiment even doesn't work because of relocation problem in crtbeginS.o My Source file: t.c #include <stdio.h> extern int foo(int argc, char **argv); void *pv1[1024]={(void*)foo,}; char aaaaa[2147483658] = {1, 2 }; char bbbbb[2147483658] = {2, 3 }; void *pv2[1024]={(void*)foo,}; int foo(int argc, char **argv) { printf("%d", aaaaa[2147483657]); printf("%d", bbbbb[2147483657]); return 0; } Command line: gcc -mcmodel=large -fPIC -shared t.c -o t.so Error: /gcc4.5.1/lib/gcc/x86_64-unknown-linux-gnu/4.5.1/crtbeginS.o: In function `__do_global_dtors_aux': crtstuff.c:(.text+0x3): relocation truncated to fit: R_X86_64_PC32 against `.bss' crtstuff.c:(.text+0x37): relocation truncated to fit: R_X86_64_PC32 against `.bss' crtstuff.c:(.text+0x57): relocation truncated to fit: R_X86_64_PC32 against `.bss' crtstuff.c:(.text+0x62): relocation truncated to fit: R_X86_64_PC32 against `.bss' crtstuff.c:(.text+0x6d): relocation truncated to fit: R_X86_64_PC32 against `.bss' Could someone help me figure out the problem? I am using RH5 64bit. My gcc is compiled with all default configuration. Thanks, Wei
next reply other threads:[~2010-10-22 1:53 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-22 1:53 liwei79 at gmail dot com [this message] 2010-10-27 20:38 ` [Bug other/46125] " pinskia at gcc dot gnu.org 2010-10-28 6:23 ` liwei79 at gmail dot com 2012-06-21 15:28 ` adrian.m.smith at gmail dot com
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-46125-4@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).