From: Jeffrey A Law <law@upchuck.cygnus.com>
To: Mark Klein <mklein@dis.com>
Cc: egcs@egcs.cygnus.com, java-discuss@sourceware.cygnus.com
Subject: Re: assemble_external on .class files
Date: Sun, 23 May 1999 19:27:00 -0000 [thread overview]
Message-ID: <12355.927512499@upchuck.cygnus.com> (raw)
In-Reply-To: <4.1.19990523114346.00c77100@garfield.dis.com>
In message < 4.1.19990523114346.00c77100@garfield.dis.com >you write:
> >Thanks ... brute force method it is! Just when I was starting to see the
> >_trees_ through the forest. :-)
>
> On further thought ... what will this do to other platforms requiring
> assemble_external? While this fix may work for PA-RISC, might it cause
> other problems elsewhere?
I do not believe so -- first most systems don't require importing symbols.
Second, we're already importing symbols which are never referenced on those
few systems that need imports.
jeff
WARNING: multiple messages have this Message-ID
From: Jeffrey A Law <law@upchuck.cygnus.com>
To: Mark Klein <mklein@dis.com>
Cc: egcs@egcs.cygnus.com, java-discuss@sourceware.cygnus.com
Subject: Re: assemble_external on .class files
Date: Mon, 31 May 1999 21:36:00 -0000 [thread overview]
Message-ID: <12355.927512499@upchuck.cygnus.com> (raw)
Message-ID: <19990531213600.FnuI66sBELEpfrja4TGukjhWTMMBzG7Mi-WmlgweLLc@z> (raw)
In-Reply-To: <4.1.19990523114346.00c77100@garfield.dis.com>
In message < 4.1.19990523114346.00c77100@garfield.dis.com >you write:
> >Thanks ... brute force method it is! Just when I was starting to see the
> >_trees_ through the forest. :-)
>
> On further thought ... what will this do to other platforms requiring
> assemble_external? While this fix may work for PA-RISC, might it cause
> other problems elsewhere?
I do not believe so -- first most systems don't require importing symbols.
Second, we're already importing symbols which are never referenced on those
few systems that need imports.
jeff
next prev parent reply other threads:[~1999-05-23 19:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-23 11:45 Mark Klein
1999-05-23 19:27 ` Jeffrey A Law [this message]
1999-05-31 21:36 ` Jeffrey A Law
1999-05-31 21:36 ` Mark Klein
-- strict thread matches above, loose matches on Subject: below --
1999-05-20 21:06 Mark Klein
1999-05-22 14:23 ` Jeffrey A Law
1999-05-22 15:28 ` Mark Klein
1999-05-31 21:36 ` Mark Klein
1999-05-25 18:33 ` Mark Klein
1999-05-25 19:41 ` Jeffrey A Law
1999-05-25 21:00 ` Per Bothner
1999-05-25 21:50 ` Jeffrey A Law
1999-05-25 22:19 ` Mark Klein
1999-05-25 22:24 ` Jeffrey A Law
1999-05-31 21:36 ` Jeffrey A Law
1999-05-25 22:49 ` Per Bothner
1999-05-31 14:53 ` Mark Klein
1999-05-31 21:36 ` Mark Klein
1999-05-31 21:36 ` Per Bothner
1999-05-31 21:36 ` Mark Klein
1999-05-31 21:36 ` Jeffrey A Law
1999-05-31 21:36 ` Per Bothner
1999-05-31 21:36 ` Jeffrey A Law
1999-05-31 21:36 ` Mark Klein
1999-05-31 21:36 ` Jeffrey A Law
1999-05-31 21:36 ` Mark Klein
[not found] <Mark>
[not found] ` <Klein's>
[not found] ` <message>
[not found] ` <of>
[not found] ` <"Tue,>
[not found] ` <25>
[not found] ` <May>
[not found] ` <1999>
[not found] ` <22:19:07>
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=12355.927512499@upchuck.cygnus.com \
--to=law@upchuck.cygnus.com \
--cc=egcs@egcs.cygnus.com \
--cc=java-discuss@sourceware.cygnus.com \
--cc=mklein@dis.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).