On October 6, 2018 10:17:48 PM GMT+02:00, Denis Khalikov
wrote:
>Hello everyone,
>this is a patch which implements EfficiencySanitizer aka ESan
>into GCC. The EfficiencySanitizer tool is available in the llvm.
>So, the main idea was to port the runtime library into GCC and
>implement GCC compiler
Uros Bizjak wrote:
> On Fri, Oct 5, 2018@1:01 AM H.J. Lu wrote:
> > diff --git a/gcc/config/i386/gnu-user.h b/gcc/config/i386/gnu-user.h
> > index a922c9b93fa..baed87aa54f 100644
> > --- a/gcc/config/i386/gnu-user.h
> > +++ b/gcc/config/i386/gnu-user.h
> > @@ -67,7 +67,7 @@ along with GCC; see th
On Wed, 18 Apr 2018, Martin Liška wrote:
> I would like to mention the attribute in GCC 8 changes.
Index: htdocs/gcc-8/changes.html
===
>
> New no_sanitize attribute has been added. The attribute
> on functions is used to
On Tue, 2 Oct 2018, David McCallum wrote:
> At this time, your Canadian mirror site at http://gcc.parentingamerica.com/
> is broken. There is only a page with the text "It works!"... which appears
> to be untrue.
Thanks for letting us know, David!
James, heads up!
For now I committed the patch b
On Fri, Oct 5, 2018 at 4:29 AM Jan Hubicka wrote:
>
> >
> > The following fixes bogus differences in scalar iteration cost
> > computed by the vectorizer when comparing 128 and 256 bit vectorizations.
> > This was caused by the hook looking at the vector types mode even
> > for kind == scalar_stmt
On 10/07/2018 06:15 AM, Gerald Pfeifer wrote:
On Wed, 18 Apr 2018, Martin Liška wrote:
I would like to mention the attribute in GCC 8 changes.
Index: htdocs/gcc-8/changes.html
===
New no_sanitize attribute has been added
This turned out to be rather more than the allocation... The ChangeLog
and the patch tell the story well enough.
Bootstraps and regtests on FC28/x86_64 - OK for trunk and later for 8-branch?
Cheers
Paul
2018-10-07 Paul Thomas
PR fortran/87151
* trans-array.c (gfc_get_array_span): De
Hi Fredrik,
> The Linux kernel requires and emulates LL and SC for the R5900 too. The
Two spaces after a full stop please (in commit descriptions too).
> special --without-llsc default for the R5900 is therefore not applicable
> in that case.
I cannot formally approve your change, but it look
While still testing an enhancement in the area of attributes
I ran across bugs and inconsistencies in how different handlers
deal with positional arguments. The bugs are either an ICE due
to the handlers not consistently converting positional arguments
to constants (i.e., CONST_DEL to INTEGER_CST
