Re: [Tinycc-devel] [PATCH] TCC arm64 back end

2015-04-16 Thread Michael Matz
Hi, On Wed, 15 Apr 2015, Thomas Preud'homme wrote: Nope. Try it for yourself: Huh, indeed. IMHO that's inconsistent with the symbol resolution behaviour of GNU ld (only looking in level0 libs for symbols, not in those DT_NEEDED by them, unless --copy-dt-needed-entries is active), but

Re: [Tinycc-devel] [PATCH] TCC arm64 back end

2015-04-15 Thread Edmund Grimley Evans
Got a patch and would appreciate some feedback. Only tested on x86-64 so far [1] so I would also appreciate testing on other targets (even i386). make test worked on arm64 and i386. ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org

Re: [Tinycc-devel] [PATCH] TCC arm64 back end

2015-04-15 Thread Thomas Preud'homme
On April 16, 2015 5:39:02 AM GMT+08:00, Edmund Grimley Evans edmund.grimley.ev...@gmail.com wrote: Got a patch and would appreciate some feedback. Only tested on x86-64 so far [1] so I would also appreciate testing on other targets (even i386). make test worked on arm64 and i386.

Re: [Tinycc-devel] [PATCH] TCC arm64 back end

2015-04-14 Thread Michael Matz
Hi, On Mon, 13 Apr 2015, Thomas Preud'homme wrote: exporting _all_ global symbols from an executable always, only symbols actually undefined in shared libs and provided by the executable are exported (included as defined in .dynsym). That's the purpose of bind_libs_dynsyms. It

Re: [Tinycc-devel] [PATCH] TCC arm64 back end

2015-04-13 Thread Michael Matz
Hello Thomas, On Sun, 12 Apr 2015, Thomas Preud'homme wrote: I was a bit puzzled because I saw symbols are resolved when a file is loaded that define them (in tcc_load_object_file). The reason this doesn't happen here is that the symbol is provided by libc.so.6 and the function that loads

Re: [Tinycc-devel] [PATCH] TCC arm64 back end

2015-04-13 Thread Thomas Preud'homme
Le lundi 13 avril 2015, 15:12:52 Michael Matz a écrit : Hello Thomas, On Sun, 12 Apr 2015, Thomas Preud'homme wrote: I was a bit puzzled because I saw symbols are resolved when a file is loaded that define them (in tcc_load_object_file). The reason this doesn't happen here is that the

Re: [Tinycc-devel] [PATCH] TCC arm64 back end

2015-04-12 Thread Thomas Preud'homme
Hi Michael, Le mercredi 11 mars 2015, 23:10:45 Thomas Preud'homme a écrit : Le dimanche 22 février 2015, 06:13:21 Michael Matz a écrit : And I pulled my hair out again when tracing the different paths the linker can go through in different modes, and how the relocs and symbol values

Re: [Tinycc-devel] [PATCH] TCC arm64 back end

2015-04-12 Thread Thomas Preud'homme
On April 12, 2015 7:02:22 PM GMT+08:00, Sergey Korshunoff sey...@gmail.com wrote: Hi, Tomas! the name resolution put the program last in the global order rather than first. Is this hard to change? It should be ok for me because I'm already familiar with the code. I will fix it this week.

Re: [Tinycc-devel] [PATCH] TCC arm64 back end

2015-03-11 Thread Edmund Grimley Evans
Thomas: And I pulled my hair out again when tracing the different paths the linker can go through in different modes, and how the relocs and symbol values change over the course of compilation. One of those days ... :-) I think that's the next thing I'm going to work on. In that case I

Re: [Tinycc-devel] [PATCH] TCC arm64 back end

2015-03-11 Thread Thomas Preud'homme
Le dimanche 22 février 2015, 06:13:21 Michael Matz a écrit : Hi, And I pulled my hair out again when tracing the different paths the linker can go through in different modes, and how the relocs and symbol values change over the course of compilation. One of those days ... :-) I think

Re: [Tinycc-devel] [PATCH] TCC arm64 back end

2015-03-11 Thread Edmund Grimley Evans
I wrote: There seems to be a general problem with TCC not using a PLT when it should. Without the PLT it works all of the time on i386 and some of the time on arm64, depending on the environment. So you really need to print the addresses that are being used to check that they are in the PLT

Re: [Tinycc-devel] [PATCH] TCC arm64 back end

2015-02-22 Thread Michael Matz
Hi, On Sun, 22 Feb 2015, Edmund Grimley Evans wrote: I've done roughly that. However, I included both fixes for VT_LLOCAL/'.', but with both disabled. Also, I omitted the VT_REF patch, of course. New diff attached, with updated README.arm64. Just for demonstration, this is what I meant

Re: [Tinycc-devel] [PATCH] TCC arm64 back end

2015-02-22 Thread Michael Matz
Hi, On Sun, 22 Feb 2015, Edmund Grimley Evans wrote: That's excellent. Many thanks. When do you sleep, by the way? :-) Roughly when you asked this question :) - merge my local uncommitted stuff or at least stash it somehow (I've implemented HFAs and have started doing va_list) - rebase my

Re: [Tinycc-devel] [PATCH] TCC arm64 back end

2015-02-21 Thread Michael Matz
Hi, On Thu, 19 Feb 2015, Edmund Grimley Evans wrote: It's not finished, but a lot of things seem to work, and there's a problem with the linker that perhaps someone could help me with. See README.arm64 for details. That's quite cool. Below is a patch on top of your's (slightly amended to

[Tinycc-devel] [PATCH] TCC arm64 back end

2015-02-19 Thread Edmund Grimley Evans
It's not finished, but a lot of things seem to work, and there's a problem with the linker that perhaps someone could help me with. See README.arm64 for details. Thanks, Edmund 2015-02-19-arm64.patch.gz Description: Binary data ___ Tinycc-devel