From: d p chang <weasel@meer.net>
To: binutils@sources.redhat.com, linux-mips@oss.sgi.com
Subject: Re: me vs gas mips64 relocation
Date: 01 Feb 2002 12:52:59 -0800 [thread overview]
Message-ID: <m2pu3o6i1g.fsf@meer.net> (raw)
In-Reply-To: <m2vgdh5n9s.fsf@meer.net>
d p chang <weasel@meer.net> writes:
> i compile this w/ (i only just added all the verbosity flags).
>
> mips64-linux-gcc -I /Volumes/Homey/dpc/Devel/linux-2.4.17/include/asm/gcc -D__KERNEL__ -I/Volumes/Homey/dpc/Devel/linux-2.4.17/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -G 0 -mno-abicalls -fno-pic -Wa,--trap -pipe -mips4 -mmad -Wa,-march=r5231 -mlong64 -mgp64 -mfp64 -ffreestanding -mabi=n32 reloc.S -c -o reloc.o -Wa,-acdhls -v -Wa,-v -Wa,-O0
Looking at this some more I realize that my problem is probably that
I'm lying to the compiler/assembler by claiming n32 and long64. We
would like to have 64 bit registers available to us in user space, but
enabling -mabi=64 gives an assertion in ld when it is trying to output
relocations for a .pdr section.
ideas? (other than for me to take the crack pipe out of my ass)
\p
---
I feel discomfort, therefore I am alive. --- Graham Greene
next prev parent reply other threads:[~2002-02-01 21:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 13:45 me vs gas mips64 relocation d p chang
2002-02-01 20:52 ` d p chang [this message]
2002-02-01 21:23 ` Eric Christopher
2002-02-03 4:47 ` d p chang
2002-02-03 7:26 ` Daniel Jacobowitz
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=m2pu3o6i1g.fsf@meer.net \
--to=weasel@meer.net \
--cc=binutils@sources.redhat.com \
--cc=linux-mips@oss.sgi.com \
--cc=weasel@cs.stanford.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.