public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hoffman at cray dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/11817] New: vargs produce 32 bit signed reference with -mcmodel=medium Date: Wed, 06 Aug 2003 01:03:00 -0000 [thread overview] Message-ID: <20030806010309.11817.hoffman@cray.com> (raw) PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11817 Summary: vargs produce 32 bit signed reference with - mcmodel=medium Product: gcc Version: 3.3 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: hoffman at cray dot com CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: x86_64-unknown-linux-gnu GCC host triplet: x86_64-unknown-linux-gnu the following snippet of code: void foo(int a,...) { } produces relocation entries as: Relocation section '.rela.text' at offset 0x4f8 contains 1 entries: Offset Info Type Sym. Value Sym. Name + Addend 00000000004b 00020000000b R_X86_64_32S 0000000000000000 .text + 83 Relocation section '.rela.eh_frame' at offset 0x510 contains 1 entries: Offset Info Type Sym. Value Sym. Name + Addend 000000000020 000200000001 R_X86_64_64 0000000000000000 .text + 0 which defeats the purpose of using -mcmodel=medium. the intent here is to link an executable at text=0x80000000, and the signed 32 bit relocation causes the linker to puke. -mcmodel=medium does express all other relocations as R_X86_64_64 (except .debug)
next reply other threads:[~2003-08-06 1:03 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-08-06 1:03 hoffman at cray dot com [this message] 2003-08-07 3:04 ` [Bug target/11817] " pinskia at physics dot uc dot edu 2003-08-07 21:53 ` hoffman at cray dot com 2003-08-08 0:07 ` hoffman at cray dot com 2003-08-23 18:32 ` pinskia at gcc dot gnu dot org 2003-09-01 5:24 ` hubicka 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=20030806010309.11817.hoffman@cray.com \ --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).