public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Sandiford <richard@codesourcery.com>
To: DJ Delorie <dj@redhat.com>
Cc: drow@false.org, gcc-patches@gcc.gnu.org
Subject: Re: mips tls with -mlong64/-mgp32
Date: Fri, 11 May 2007 12:54:00 -0000	[thread overview]
Message-ID: <87wszf8qr3.fsf@firetop.home> (raw)
In-Reply-To: <200705111222.l4BCMmn1029370@greed.delorie.com> (DJ Delorie's 	message of "Fri, 11 May 2007 08:22:48 -0400")

DJ Delorie <dj@redhat.com> writes:
>> Hmm, which GOT values do you mean?  Pointers in the GOT ought to be 32 bits.
>
> mips64vrel-elf
> gcc.dg/tls/nonpic-1.c
> ./cc1 nonpic-1.i -meb -quiet -mabi=eabi -mlong64 -mgp32 -ftls-model=initial-exec
>
> Trimmed test case:
>
> extern __thread long e1;
> long ge1 (void)
> {
>   return e1;
> }

That doesn't really answer the question though. ;)  I don't have a
mips64vr-elf compiler handy, so it'd be helpful if you could just
tell me what sort of GOT entry is 64 bits wide and how it ends up
so wide.

Richard

  reply	other threads:[~2007-05-11 12:54 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10 20:46 DJ Delorie
2007-05-10 21:24 ` Daniel Jacobowitz
2007-05-10 21:27   ` DJ Delorie
2007-05-10 21:38     ` Daniel Jacobowitz
2007-05-11  1:07       ` DJ Delorie
2007-05-11  3:24         ` Daniel Jacobowitz
2007-05-11  7:22         ` Rask Ingemann Lambertsen
2007-05-11  7:31           ` Andrew Pinski
2007-05-11 11:47           ` Daniel Jacobowitz
2007-05-11 12:17             ` DJ Delorie
2007-05-11 12:16     ` Richard Sandiford
2007-05-11 12:24       ` DJ Delorie
2007-05-11 12:54         ` Richard Sandiford [this message]
2007-05-11 13:07           ` DJ Delorie
2007-05-11 13:16             ` Paolo Bonzini
2007-05-11 13:19             ` Richard Sandiford
2007-05-11 13:33               ` Daniel Jacobowitz
2007-05-11 13:43                 ` Richard Sandiford
2007-05-15 20:39                   ` DJ Delorie
2007-05-17 19:12                   ` DJ Delorie
2007-05-17 19:28                     ` Richard Sandiford
2007-05-17 19:50                       ` DJ Delorie
2007-05-17 20:02                         ` Richard Sandiford
2007-05-17 20:05                           ` Richard Sandiford
2007-05-17 20:07                             ` DJ Delorie
2007-05-17 20:10                           ` DJ Delorie
2007-05-17 20:12                             ` Richard Sandiford
2007-05-17 20:56                               ` DJ Delorie
2007-05-17 21:35                                 ` Richard Sandiford
2007-05-17 23:08                                   ` DJ Delorie
2007-05-18  7:02                                     ` Richard Sandiford
2007-05-18  9:58                                       ` Richard Sandiford
2007-05-18 21:23                                       ` DJ Delorie
2007-05-19  6:33                                         ` Richard Sandiford
2007-05-19 14:51                                           ` DJ Delorie
2007-05-19  7:33                                         ` Richard Sandiford
2007-05-19 14:57                                           ` DJ Delorie
2007-05-17 20:13                           ` DJ Delorie

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=87wszf8qr3.fsf@firetop.home \
    --to=richard@codesourcery.com \
    --cc=dj@redhat.com \
    --cc=drow@false.org \
    --cc=gcc-patches@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).