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 target/11817] vargs produce 32 bit signed reference with -mcmodel=medium
Date: Fri, 08 Aug 2003 00:07:00 -0000	[thread overview]
Message-ID: <20030808000716.16086.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030806010309.11817.hoffman@cray.com>

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



------- Additional Comments From hoffman at cray dot com  2003-08-08 00:07 -------

  -mcmodel changes the way that all references requiring 
   relocation are coded, causing the assembler to produce
   the correct code. 'medium' mode introduces an intermediate
   64 bit register to store the address

  the presence of varargs in a function on 64 bit causes a spill 
  of the mmx registers, conditional on another register being
  nonzero (as defined in the x86_64 abi)

  this spill is handled by ix86_setup_incoming_varags in
  gcc/config/i386/i386.c

  this calls a pseudo-instruction, see_prologue_save_insn
  in gcc/config/i386/i386.md

  the generation of the computed target at the end of the
  jump doesn't follow the game generation rule as normal
  references, and forces the compiler to issue the signed
  32 bit reference, which screws up our link


  parent reply	other threads:[~2003-08-08  0:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-06  1:03 [Bug c/11817] New: " hoffman at cray dot com
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 [this message]
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=20030808000716.16086.qmail@sources.redhat.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: link
Be 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).