public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dale Johannesen <dalej@apple.com>
To: Geoffrey Keating <geoffk@apple.com>
Cc: Dale Johannesen <dalej@apple.com>, Geert Bosch <bosch@gnat.com>,
	gcc@gcc.gnu.org
Subject: Re: Problems building GNAT on OS X with top-of-tree
Date: Thu, 17 Oct 2002 17:06:00 -0000	[thread overview]
Message-ID: <B98A34F3-E21A-11D6-B07C-000393D76DAA@apple.com> (raw)
In-Reply-To: <BCC615EC-E218-11D6-A20F-0030657EA24A@apple.com>


On Thursday, October 17, 2002, at 02:38  PM, Geoffrey Keating wrote:
> On Thursday, October 17, 2002, at 02:10  PM, Dale Johannesen wrote:
>>
>> Actually this looks like it is connected to Geoff's recent patch
>> http://gcc.gnu.org/ml/gcc-patches/2002-09/msg01259.html
>> which introduced the LSJR label.  Geoff, is
>> current_function_uses_pic_offset_table not getting set anywhere?
>> That would account for his symptom.
>>
> It is supposed to be set by machopic_function_base_name, which is 
> called to generate the label.  Looking at the code, my suspicion is 
> that  the original load_macho_picbase pattern is getting deleted by 
> flow because it appears dead, but that also deletes the label that the 
> macho_correct_pic needs.
>
> If so, the solution is to use a real CODE_LABEL instead of having the 
> label inside load_macho_picbase, but this will be a complex change.

Hmm.  How do you keep the bcl and the following label together through 
the scheduler?
SCHED_GROUP_P used to work on labels, but it doesn't any more, and I 
never found
another way to do it.  Would a USE of the label work?

>> (This is probably unrelated to your earlier bug.)
>
> Well, it's certainly related, in the sense that if I hadn't fixed that 
> bug this code would now fail at runtime instead of compile-time…

(I meant Geert Bosch's earlier bug, not yours.  Sorry to be unclear.)

  reply	other threads:[~2002-10-17 21:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E5B21272-E13A-11D6-B07C-000393D76DAA@apple.com>
2002-10-16 13:28 ` Geert Bosch
2002-10-16 15:00   ` Dale Johannesen
2002-10-17 14:52     ` Geert Bosch
2002-10-17 15:00       ` Dale Johannesen
2002-10-17 15:02       ` Dale Johannesen
2002-10-17 15:22         ` Geoffrey Keating
2002-10-17 17:06           ` Dale Johannesen [this message]
2002-10-17 20:59             ` Geoffrey Keating
2002-10-15 21:08 Geert Bosch
2002-10-16 10:43 ` Dale Johannesen
2002-10-16 10:59 ` Dale Johannesen
2002-10-16 11:30   ` Geert Bosch
2002-10-16 11:48     ` Dale Johannesen
2002-10-16 13:14       ` Geert Bosch

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=B98A34F3-E21A-11D6-B07C-000393D76DAA@apple.com \
    --to=dalej@apple.com \
    --cc=bosch@gnat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=geoffk@apple.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).