On Fri, Feb 15, 2019 at 3:30 AM Steve Ellcey wrote:
>
> I have a question about SPEC CPU 2017 and what GCC can and cannot do
> with -flto. As part of some SPEC analysis I am doing I found that with
> -Ofast, ICC and GCC were not that far apart (especially spec int rate,
> spec fp rate was a sligh
Bin.Cheng 于2019年2月15日周五 下午5:12写道：
> On Fri, Feb 15, 2019 at 3:30 AM Steve Ellcey wrote:
> >
> > I have a question about SPEC CPU 2017 and what GCC can and cannot do
> > with -flto. As part of some SPEC analysis I am doing I found that with
> > -Ofast, ICC and GCC were not that far apart (especi
I never could understand, why field reordering was removed from GCC? I
mean, I know that it's prohibited in C and C++, but, sure, GCC can
detect whether it possibly can influence application behavior, and if
not, just do the reorder.
The veto is important to C/C++ as programming languages, but not
On February 15, 2019 1:45:10 PM GMT+01:00, Hi-Angel
wrote:
>I never could understand, why field reordering was removed from GCC?
The implementation simply was seriously broken, bitrotten and unmaintained.
Richard
I
>mean, I know that it's prohibited in C and C++, but, sure, GCC can
>detect
On Fri, Feb 15, 2019 at 02:12:27PM +0100, Richard Biener wrote:
> On February 15, 2019 1:45:10 PM GMT+01:00, Hi-Angel
> wrote:
> >I never could understand, why field reordering was removed from GCC?
>
> The implementation simply was seriously broken, bitrotten and unmaintained.
Which of course
On Fri, Feb 15, 2019 at 1:16 PM Jakub Jelinek wrote:
>
> On Fri, Feb 15, 2019 at 02:12:27PM +0100, Richard Biener wrote:
> > On February 15, 2019 1:45:10 PM GMT+01:00, Hi-Angel
> > wrote:
> > >I never could understand, why field reordering was removed from GCC?
> >
> > The implementation simply
On Fri, Feb 15, 2019 at 4:46 AM Hi-Angel wrote:
>
> I never could understand, why field reordering was removed from GCC? I
> mean, I know that it's prohibited in C and C++, but, sure, GCC can
> detect whether it possibly can influence application behavior, and if
> not, just do the reorder.
>
> Th
The first release candidate for GCC 8.3 is available from
https://gcc.gnu.org/pub/gcc/snapshots/8.3.0-RC-20190215/
ftp://gcc.gnu.org/pub/gcc/snapshots/8.3.0-RC-20190215/
and shortly its mirrors. It has been generated from SVN revision 268935.
I have so far bootstrapped and tested the release
Status
==
The GCC 8 branch is now frozen for blocking regressions and documentation
fixes only, all changes to the branch require a RM approval now.
Quality Data
Priority # Change from last report
--- ---
P10
P2
On Fri, 2019-02-15 at 17:48 +0800, Jun Ma wrote:
>
> ICC is doing much more than GCC in ipo, especially memory layout
> optimizations. See https://software.intel.com/en-us/node/522667.
> ICC is more aggressive in array transposition/structure splitting
> /field reordering. However, these optimiza
On Fri, Feb 15, 2019 at 9:02 AM Ian Lance Taylor wrote:
> On Fri, Feb 15, 2019 at 4:46 AM Hi-Angel wrote:
> >
> > I never could understand, why field reordering was removed from GCC? I
> > mean, I know that it's prohibited in C and C++, but, sure, GCC can
> > detect whether it possibly can influ
On Thu, Feb 14, 2019 at 11:33 PM Paulo Matos wrote:
> Are global variables not supposed to alias each other?
> If I indeed do that, gcc still won't group loads and stores:
> https://cx.rv8.io/g/rFjGLa
I meant something like
struct foo_t x, y;
and now they clearly don't alias. As global pointers
> Hasn't GNAT sorted Ada elements in records (e.g. structures) by size
> since near its initial addition to GCC in the mid-90s?
No, it wasn't done early on and it was never done in that major a way
now. Most reordering (possibly all; I'm not sure) is done between
objects of variable and fixed si
On 15/02/2019 19:15, Jim Wilson wrote:
> On Thu, Feb 14, 2019 at 11:33 PM Paulo Matos wrote:
>> Are global variables not supposed to alias each other?
>> If I indeed do that, gcc still won't group loads and stores:
>> https://cx.rv8.io/g/rFjGLa
>
> I meant something like
> struct foo_t x, y;
>
> Hasn't GNAT sorted Ada elements in records (e.g. structures) by size
> since near its initial addition to GCC in the mid-90s? This results in the
> largest elements up front and minimizes the need for alignment gaps.
No, that's a serious misconception, since one of the features of GNAT is to be
On 02/15/19 10:13, Jakub Jelinek wrote:
The first release candidate for GCC 8.3 is available from
https://gcc.gnu.org/pub/gcc/snapshots/8.3.0-RC-20190215/
ftp://gcc.gnu.org/pub/gcc/snapshots/8.3.0-RC-20190215/
and shortly its mirrors. It has been generated from SVN revision 268935.
I
Snapshot gcc-8-20190215 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/8-20190215/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 8 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-8
Découvrez la société d’artisans LEON située à NOZAY en Essonne. Nous
sommes les spécialistes régionaux de la toiture. Nous exerçons dans ce domaine
de père en fils depuis 4 générations. Les tuiles, liteaux, gouttières n’ont
aucuns secrets pour nous, pas plus que le zinc ou l’étanchéisation.Notre
On Tue, 2019-02-12 at 15:12 +0100, Richard Biener wrote:
> On Mon, Feb 11, 2019 at 10:46 PM Giuliano Belinassi
> wrote:
> >
> > Hi,
> >
> > I was just wondering what API should I use to spawn threads and
> > control
> > its flow. Should I use OpenMP, pthreads, or something else?
> >
> > My poin
19 matches
Mail list logo
