public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: Jeffrey A Law <law@cygnus.com>
Cc: egcs@egcs.cygnus.com
Subject: Re: Should asm("" : : : "memory") order accesses to the GOT?
Date: Thu, 17 Jun 1999 14:17:00 -0000	[thread overview]
Message-ID: <99061723185900.00938@ns1102.munich.netsurf.de> (raw)
In-Reply-To: <11478.929652123@upchuck.cygnus.com>

Am Don, 17 Jun 1999 schrieb Jeffrey A Law:
>In message < 99061722151000.00879@ns1102.munich.netsurf.de >you write:
>  > the subject says it all, should address loads from the GOT considered as
>  > memory accesses?
>It should.  But typically we do not represent GOT references as memory
>references. 
>
>This is a fairly generic problem with our PIC code in the sense that we're
>lying to the compiler about what the machine actually does.  Lots of ports
>have the same problem.
>
>If we ever revamp how we represent PIC internally, this is one of the problems
>I want to fix :-)

Hmm, sounds like a big task. So there's currently no way to order accesses to
the GOT in gcc, independent of platform. Then the only way to fix ld.so is to
move these accesses out into a different file.

BTW, Geoff suggested to replace all unspec 8 with something like this:
(define_expand "movsi_got"
  [(set (match_operand:SI 0 "register_operand" "")
        (mem (plus (unspec [(match_operand:SI 1 "got_operand" "")] 8)
                 (match_dup 2))))]


But if all platforms are affected it's better to fix glibc once and forever.

Franz.

WARNING: multiple messages have this Message-ID
From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: Jeffrey A Law <law@cygnus.com>
Cc: egcs@egcs.cygnus.com
Subject: Re: Should asm("" : : : "memory") order accesses to the GOT?
Date: Wed, 30 Jun 1999 15:43:00 -0000	[thread overview]
Message-ID: <99061723185900.00938@ns1102.munich.netsurf.de> (raw)
Message-ID: <19990630154300.UsoKIUugJIsIzLSiM2kzkhMysshfDq8oshwYQYWxowE@z> (raw)
In-Reply-To: <11478.929652123@upchuck.cygnus.com>

Am Don, 17 Jun 1999 schrieb Jeffrey A Law:
>In message < 99061722151000.00879@ns1102.munich.netsurf.de >you write:
>  > the subject says it all, should address loads from the GOT considered as
>  > memory accesses?
>It should.  But typically we do not represent GOT references as memory
>references. 
>
>This is a fairly generic problem with our PIC code in the sense that we're
>lying to the compiler about what the machine actually does.  Lots of ports
>have the same problem.
>
>If we ever revamp how we represent PIC internally, this is one of the problems
>I want to fix :-)

Hmm, sounds like a big task. So there's currently no way to order accesses to
the GOT in gcc, independent of platform. Then the only way to fix ld.so is to
move these accesses out into a different file.

BTW, Geoff suggested to replace all unspec 8 with something like this:
(define_expand "movsi_got"
  [(set (match_operand:SI 0 "register_operand" "")
        (mem (plus (unspec [(match_operand:SI 1 "got_operand" "")] 8)
                 (match_dup 2))))]


But if all platforms are affected it's better to fix glibc once and forever.

Franz.

  reply	other threads:[~1999-06-17 14:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-17 13:13 Franz Sirl
1999-06-17 13:44 ` David S. Miller
1999-06-17 14:17   ` Franz Sirl
1999-06-17 14:21     ` David S. Miller
1999-06-17 14:45       ` Franz Sirl
1999-06-30 15:43         ` Franz Sirl
1999-06-30 15:43       ` David S. Miller
1999-06-30 15:43     ` Franz Sirl
1999-06-30 15:43   ` David S. Miller
1999-06-17 13:47 ` Jeffrey A Law
1999-06-17 14:17   ` Franz Sirl [this message]
1999-06-17 22:30     ` Jeffrey A Law
1999-06-30 15:43       ` Jeffrey A Law
1999-06-30 15:43     ` Franz Sirl
1999-06-30 15:43   ` Jeffrey A Law
1999-06-30 15:43 ` Franz Sirl

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=99061723185900.00938@ns1102.munich.netsurf.de \
    --to=franz.sirl-kernel@lauterbach.com \
    --cc=egcs@egcs.cygnus.com \
    --cc=law@cygnus.com \
    /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).