From: "Zack Weinberg" <zack@codesourcery.com>
To: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
Cc: Eric Christopher <echristo@redhat.com>,
Alexandre Oliva <aoliva@redhat.com>,
"Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
Atsushi Nemoto <nemoto@toshiba-tops.co.jp>,
linux-mips@linux-mips.org, binutils@sources.redhat.com
Subject: Re: recent binutils and mips64-linux
Date: Tue, 23 Sep 2003 13:06:03 -0700 [thread overview]
Message-ID: <87ad8vb784.fsf@codesourcery.com> (raw)
In-Reply-To: <20030923200337.GE18698@rembrandt.csv.ica.uni-stuttgart.de> (Thiemo Seufer's message of "Tue, 23 Sep 2003 22:03:37 +0200")
Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de> writes:
> Zack Weinberg wrote:
>>
>> Maybe what you really want is an -mdata-model=kernel switch (or some
>> such spelling)
>
> Well, an ELF64 kernel loaded in the 64bit address space is also legal,
> and desireable on some (bigger) hardware. Btw, it would have to be
> -mtext-model=kernel, the data is the same. :-)
Well, you wouldn't compile such a kernel with that switch. Maybe
spelling it -mtext-model=kseg0 would be more descriptive.
>> that tells gcc to do the right thing in the first place?
>
> Gcc still generates MIPS assembler macros, so such a switch would
> do nothing yet. Gcc should be changed to do the expansion itself
> (and improve code quality by that), but that's a much larger task.
Gcc can at least pass the setting along to the assembler (which would
have to grow such an option as well, either as a command line switch
or (preferred) a .directive).
zw
next prev parent reply other threads:[~2003-09-23 20:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 21:27 recent binutils and mips64-linux Daniel Jacobowitz
2003-09-19 2:58 ` Eric Christopher
2003-09-19 3:29 ` Atsushi Nemoto
2003-09-19 3:28 ` Daniel Jacobowitz
2003-09-19 7:23 ` Atsushi Nemoto
2003-09-19 5:39 ` Eric Christopher
2003-09-19 12:52 ` Maciej W. Rozycki
2003-09-19 16:20 ` Eric Christopher
2003-09-19 16:41 ` Thiemo Seufer
2003-09-19 16:46 ` Maciej W. Rozycki
2003-09-19 17:08 ` Thiemo Seufer
2003-09-19 17:19 ` Maciej W. Rozycki
2003-09-19 17:40 ` Thiemo Seufer
2003-09-19 18:14 ` Maciej W. Rozycki
2003-09-19 18:28 ` David Kesselring
2003-09-22 21:26 ` Alexandre Oliva
2003-09-22 21:31 ` Daniel Jacobowitz
2003-09-22 23:39 ` Thiemo Seufer
2003-09-23 1:21 ` Eric Christopher
2003-09-23 8:14 ` Thiemo Seufer
2003-09-23 18:01 ` Eric Christopher
2003-09-23 18:16 ` Daniel Jacobowitz
2003-09-23 19:45 ` Zack Weinberg
2003-09-23 19:56 ` Daniel Jacobowitz
2003-09-23 20:03 ` Thiemo Seufer
2003-09-23 20:06 ` Zack Weinberg [this message]
2003-09-23 20:18 ` Thiemo Seufer
2003-09-23 20:28 ` Eric Christopher
2003-09-19 16:42 ` Maciej W. Rozycki
2003-09-19 16:57 ` Thiemo Seufer
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=87ad8vb784.fsf@codesourcery.com \
--to=zack@codesourcery.com \
--cc=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=echristo@redhat.com \
--cc=ica2_ts@csv.ica.uni-stuttgart.de \
--cc=linux-mips@linux-mips.org \
--cc=macro@ds2.pg.gda.pl \
--cc=nemoto@toshiba-tops.co.jp \
/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