- On May 16, 2024, at 5:46 PM, 赵爱南 zhaoainan...@163.com wrote:
> Hello everyone:
> I'm nanzhu ,I want to know how to add new ELF e_machine value and what do I
> need to prepare .Then how to add a new architecture to the open source
> community,thanks.
To have a new e_machine value assign
> BFD's behavior becomes very problematic with LTO: archive index does not
> distinguish between normal and common definitions, and there's no explicit
> plugin API to check if a definition in IR is "common", so the linker has to
> round-trip via the plugin in a fairly convoluted way to emulate the
I was just using g++ as the linker driver, not to compile the objects.
I linked with the objects you provided, which had been compiled by
clang. Linking just those objects by themselves produces no warnings
at all, since the "tempnam" warning comes from libc.
On Fri, Jul 13, 2018 at 12:05 PM, lpha
Got it now -- sorry, problem on my end.
On Fri, Jul 13, 2018 at 11:14 AM, lpham54321 at gmail dot com
wrote:
> https://sourceware.org/bugzilla/show_bug.cgi?id=23258
>
> --- Comment #4 from Lan ---
> hmm ... worked just fine for me.
>
> lans-mbp:downloads lanpham$ tar -xvf bug_23258.tar
> x bug_2
> It boils down to reading a character 'c' off the string and then translating
> it
> through a lookup table to a UTF-16 code point:
>
> private static immutable dchar m_charMapStart = 0xa1;
> private static immutable dchar m_charMapEnd = 0xff;
>
> private immutable wstring charMap =
>
> Please show the command line used to compile pr20308_gd.o.
>
> BTW, did you run "make clean" first?
Yeah, the build rules should also have a dependency on gcctestdir/as.
Forgot that when fixing the x86_64 test, sorry.
-cary
___
bug-binutils mailing l
