On Sat, Dec 26, 2020 at 5:41 PM Rhys Rustad-Elliott wrote:
>
> Hi all,
>
> I've encountered a strange issue when compiling C to a flat binary with GCC.
> It's questionably a bug, but I hesitate to strongly say that due to my lack of
> familiarity with the GCC codebase and the rather obscure nature
Hi all,
I've encountered a strange issue when compiling C to a flat binary with GCC.
It's questionably a bug, but I hesitate to strongly say that due to my lack of
familiarity with the GCC codebase and the rather obscure nature of what I'm
trying to do. Posting this here in the hopes that someone
King—hawlery
Snapshot gcc-10-20201226 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/10-20201226/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 10 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
On Sat, Dec 26, 2020 at 7:32 AM Florian Weimer wrote:
>
> * Fangrui Song:
>
> > Hi, I filed https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98112 which
> > proposes -fdirect-access-external-data to address some x86-64
> > GCC/binutils pain[1] and also benefit non-x86 architectures (also see [1]
> > i
* Fangrui Song:
> Hi, I filed https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98112 which
> proposes -fdirect-access-external-data to address some x86-64
> GCC/binutils pain[1] and also benefit non-x86 architectures (also see [1]
> it can prevent copy relocations).
>
> [1] Mentioned in https://gcc.gn
