Snapshot gcc-11-20200712 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/11-20200712/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 11 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Hi，
I consider four ways to implementation it,
and maybe we can use ‘csplit’ tool to split output file, is that right ?
—Jojo
在 2020年7月9日 +0800 PM3:59，Martin Liška ，写道：
> On 7/9/20 9:54 AM, jiejie_r...@c-sky.com wrote:
> > Hi,
> >
> > The size of generated file like insn-emit.c i
On Fri, Jul 10, 2020 at 11:45 PM H.J. Lu via Gcc wrote:
>
> On Fri, Jul 10, 2020 at 10:30 AM Florian Weimer wrote:
> >
> > Most Linux distributions still compile against the original x86-64
> > baseline that was based on the AMD K8 (minus the 3DNow! parts, for Intel
> > EM64T compatibility).
> >
Again, Debian 9. Doing "git gcc-backport a4aca1edaf37d43" on
releases/gcc-10 gave me:
[releases/gcc-10 83cf5a7c6a5] PR94600: fix volatile access to the whole of a
compound object.
Date: Sun Jul 5 20:50:52 2020 +0200
9 files changed, 276 insertions(+), 1 deletion(-)
create mode 100644 gcc/test
* H. J. Lu:
> Looks good. I like it.
Thanks. What do you think about Level B? Should we keep it?
> My only concerns are
>
> 1. Names like “x86-100”, “x86-101”, what features do they support?
I think we can add more diagnostic output to ld.so --help. My patch
does not show individual CPU fla
* Allan Sandfeld Jensen:
> On Freitag, 10. Juli 2020 19:30:09 CEST Florian Weimer via Gcc wrote:
>> glibc (or an alternative loader implementation) would search for
>> libraries starting at level D, going back to level A, and finally the
>> baseline implementation in the default library location.
