From: Dale Johannesen <dalej@apple.com>
To: Geert Bosch <bosch@gnat.com>
Cc: Dale Johannesen <dalej@apple.com>, gcc@gcc.gnu.org
Subject: Re: Problems building GNAT on OS X with top-of-tree
Date: Wed, 16 Oct 2002 15:00:00 -0000 [thread overview]
Message-ID: <F0F8275F-E149-11D6-B07C-000393D76DAA@apple.com> (raw)
In-Reply-To: <DD3D5C3B-E140-11D6-A8D0-00039344BF4A@gnat.com>
On Wednesday, October 16, 2002, at 12:52 PM, Geert Bosch wrote:
> OK, I see. Indeed, using -fno-common eliminates/suppresses the problem.
> However, I don't see how the front end should have to know
> about these details. I looked at darwin.c, and I see the implementation
> of the scheme using lazy and non-lazy pointers, but there does not
> seem to be any documentation at a sufficiently high level to be able
> to understand what is going on there.
Right. I didn't write it, and I still find it confusing.
> I'm focussing now on finding out why this problems does not occur with
> the C front end, which seems to use the same method for outputting
> variables in the common section.
You could do that. Alternatively, I see that the correct sequence is
generated for ada__exceptions__null_occurrence, which is also a .comm
symbol. You might look and see what's different about the symbols.
This is probably just a matter of getting some field set correctly.
next prev parent reply other threads:[~2002-10-16 20:58 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 [this message]
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
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=F0F8275F-E149-11D6-B07C-000393D76DAA@apple.com \
--to=dalej@apple.com \
--cc=bosch@gnat.com \
--cc=gcc@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).