Thanks for the fixes. I made some style tweaks, committed as follows
after bootstrap and testing.
Ian
2017-10-02 Ian Lance Taylor
* ztest.c: #include .
(TEST_TIMING): Don't define, don't test.
(xclock_gettime, xclockid_t): Define if !HAVE_CLOCK_GETTIME.
(clockid_t, clock_gettime, CLOCK_REALT
On Mon, 2 Oct 2017, Michael Meissner wrote:
> > > But in any case, the new macro should be documented in cpp.texi alongside
> > > the existing __FP_FAST_FMA* macros (probably in the generic
> > > __FP_FAST_FMAF@var{n} and __FP_FAST_FMAF@var{n}X form).
> >
> > This patch adds support for adding
On 10/02/2017 05:29 PM, Steve Ellcey wrote:
On Mon, 2017-10-02 at 17:00 -0600, Martin Sebor wrote:
The attached patch tweaks the configuration check for attribute
ifunc support in libatomic to avoid the new type safety warnings.
It also changes the libatomic declarations of ifunc resolvers to
av
Whoops, I forgot to attach the patch.
On Mon, Oct 02, 2017 at 07:51:00PM -0400, Michael Meissner wrote:
> On Thu, Sep 28, 2017 at 12:40:24AM +, Joseph Myers wrote:
> > On Wed, 27 Sep 2017, Michael Meissner wrote:
> >
> > > The glibc team has requested we define the standard macro
> > > (__FP
On Thu, Sep 28, 2017 at 12:40:24AM +, Joseph Myers wrote:
> On Wed, 27 Sep 2017, Michael Meissner wrote:
>
> > The glibc team has requested we define the standard macro
> > (__FP_FAST_FMAF128)
> > for PowerPC code when we have the IEEE 128-bit floating point hardware
> > instructions enabled.
On Mon, 2017-10-02 at 17:00 -0600, Martin Sebor wrote:
> The attached patch tweaks the configuration check for attribute
> ifunc support in libatomic to avoid the new type safety warnings.
> It also changes the libatomic declarations of ifunc resolvers to
> avoid the new warnings. With it conftest
On Mon, 2 Oct 2017, Martin Sebor wrote:
> The attached patch tweaks the configuration check for attribute
> ifunc support in libatomic to avoid the new type safety warnings.
> It also changes the libatomic declarations of ifunc resolvers to
> avoid the new warnings. With it conftest.c compiles su
The attached patch tweaks the configuration check for attribute
ifunc support in libatomic to avoid the new type safety warnings.
It also changes the libatomic declarations of ifunc resolvers to
avoid the new warnings. With it conftest.c compiles successfully
(see below) as does libatomic, and no
On 02/10/17 21:53 +0200, Jakub Jelinek wrote:
On Mon, Oct 02, 2017 at 03:13:17PM +0100, Jonathan Wakely wrote:
This adds the integral overloads of std::to_chars and std::from_chars,
including the changes made by P0682R0. Support for floating point types
is absent.
This uses a number of suggesti
On 10/02/2017 01:35 PM, Segher Boessenkool wrote:
> If we have (X&C1)|C2 simplify_binary_operation_1 makes C1 as small as
> possible. This makes worse code in common cases like when the AND with
> C1 is from a zero-extension. This patch fixes it by removing this
> transformation (twice).
>
> I t
On 09/28/2017 05:50 AM, Andreas Krebbel wrote:
> gcc/ChangeLog:
>
> 2017-09-28 Andreas Krebbel
>
> * doc/sourcebuild.texi: Document vect_can_peel.
>
> gcc/testsuite/ChangeLog:
>
> 2017-09-28 Andreas Krebbel
>
> * g++.dg/vect/slp-pr56812.cc: xfail for targets which don't want
On 09/28/2017 05:50 AM, Andreas Krebbel wrote:
> gcc/ChangeLog:
>
> 2017-09-28 Andreas Krebbel
>
> * doc/sourcebuild.texi: Document vect_intdouble_cvt and
> vect_doubleint_cvt.
>
> gcc/testsuite/ChangeLog:
>
> 2017-09-28 Andreas Krebbel
>
> * gcc.dg/vect/pr66251.c: Repl
On 09/28/2017 05:50 AM, Andreas Krebbel wrote:
> Testcases which override the vect default options using dg-options
> need at least -mzarch on S/390 32 bit.
>
> gcc/testsuite/ChangeLog:
>
> 2017-09-28 Andreas Krebbel
>
> * gfortran.dg/vect/fast-math-mgrid-resid.f: Use -mzarch on S/390.
On 09/28/2017 05:50 AM, Andreas Krebbel wrote:
> The target supports routines provide vect_double and vect_float but
> these do not appear to be used consequently in the vect testcases.
> With z13 we only have support for vector double but with z14 also for
> vector float. This patch adds vect_flo
On 09/28/2017 05:50 AM, Andreas Krebbel wrote:
> We don't have a 64 bit vector integer multiply on z. Add a specific
> check for that.
>
> gcc/ChangeLog:
>
> 2017-09-28 Andreas Krebbel
>
> * doc/sourcebuild.texi: Document vect_long_mult.
>
> gcc/testsuite/ChangeLog:
>
> 2017-09-28 A
On 08/08/2017 10:13 AM, Martin Sebor wrote:
> Patch 3 in the series restores the diagnostics for conflicting
> attribute aligned on the same function (this regressed in r192199
> in GCC 4.9), and also makes use of the enhanced infrastructure to
> enhance the detection of the same conflicts on disti
On 08/08/2017 10:13 AM, Martin Sebor wrote:
> Part 2 of the series contains the mechanical changes to all
> the back ends and to front ends other than C and C++. There
> are no functional changes here.
>
> Martin
>
>
> gcc-81544-2.diff
>
>
> PR c/81544 - attribute noreturn and warn_unused_res
On 09/20/2017 12:04 PM, Martin Sebor wrote:
> On 09/19/2017 03:00 PM, Joseph Myers wrote:
>> On Tue, 19 Sep 2017, Martin Sebor wrote:
>>
In general, the data structures where you need to ensure manually that if
attribute A is listed in EXCL for B, then attribute B is also listed in
>
On 08/10/2017 01:29 PM, Martin Sebor wrote:
>>> diff --git a/gcc/builtins.c b/gcc/builtins.c
>>> index 016f68d..1aa9e22 100644
>>> --- a/gcc/builtins.c
>>> +++ b/gcc/builtins.c
>> [ ... ]
>>> +
>>> + if (TREE_CODE (type) == ARRAY_TYPE)
>>> + {
>>> + /* Return the constant size unless it's
I have committed the appended patch to update the GCC 7 branch to the
Go 1.8.3 release of the Go standard library. The branch was
previously on the Go 1.8.1 release. This is a fairly small patch that
fixes various bugs, a subset of the ones listed at:
https://github.com/golang/go/issues?q=is%3Ai
On Mon, 2017-10-02 at 16:22 -0400, Paul Koning wrote:
> > On Oct 2, 2017, at 4:05 PM, David Malcolm
> > wrote:
> >
> > ...
> > the C FE currently emits (trunk):
> >
> > test.c: In function 'caller':
> > test.c:5:25: warning: passing argument 2 of 'callee' makes pointer
> > from
> > integer wi
> On Oct 2, 2017, at 4:05 PM, David Malcolm wrote:
>
> ...
> the C FE currently emits (trunk):
>
> test.c: In function 'caller':
> test.c:5:25: warning: passing argument 2 of 'callee' makes pointer from
> integer without a cast [-Wint-conversion]
> return callee (first, second, third);
>
On 10/02/2017 01:49 PM, Steve Ellcey wrote:
On Wed, 2017-09-20 at 08:37 -0700, Steve Ellcey wrote:
On Tue, 2017-09-19 at 09:16 -0600, Martin Sebor wrote:
On 09/18/2017 03:44 PM, Joseph Myers wrote:
On Mon, 18 Sep 2017, Martin Sebor wrote:
It's meant as an escape hatch. It allows declaring
co
In r253096
("C++: underline parameters in mismatching function calls"
aka 5d78d423a5f7a1d135c7bb678e82007678d1313c
https://gcc.gnu.org/ml/gcc-patches/2017-09/msg01546.html )
I updated the C++ FE's handling of mismatched types in function calls
so that it underlines the pertinent param of th
On Mon, Oct 02, 2017 at 03:13:17PM +0100, Jonathan Wakely wrote:
> This adds the integral overloads of std::to_chars and std::from_chars,
> including the changes made by P0682R0. Support for floating point types
> is absent.
>
> This uses a number of suggestions from Lars (thanks!) but I might hav
On Mon, 2 Oct 2017, Steve Ellcey wrote:
> I think there is more fallout from this patch. The libatomic library
> can use ifuncs and right now it is not working on aarch64 (testing a
> proposed patch I sent) because the ifunc check fails due to the new
> warnings. I believe this can be reproduced
On Wed, 2017-09-20 at 08:37 -0700, Steve Ellcey wrote:
> On Tue, 2017-09-19 at 09:16 -0600, Martin Sebor wrote:
> > On 09/18/2017 03:44 PM, Joseph Myers wrote:
> > > On Mon, 18 Sep 2017, Martin Sebor wrote:
> > > > It's meant as an escape hatch. It allows declaring
> > > > compatibility
> > > > sy
If we have (X&C1)|C2 simplify_binary_operation_1 makes C1 as small as
possible. This makes worse code in common cases like when the AND with
C1 is from a zero-extension. This patch fixes it by removing this
transformation (twice).
I tested this on 31 targets, also some variations that do the
tra
Hi!
On Mon, Oct 02, 2017 at 02:01:57PM -0400, Michael Meissner wrote:
> On Fri, Sep 29, 2017 at 12:10:07PM -0500, Segher Boessenkool wrote:
> > On Thu, Sep 28, 2017 at 06:34:23PM -0400, Michael Meissner wrote:
> > > --- gcc/config/rs6000/rs6000.md (revision 253267)
> > > +++ gcc/config/rs6000/rs
Committed as revision 253362.
Thanks for taking a look at it. I will wait a week or so before
committing to 7-branch.
Paul
On 1 October 2017 at 14:43, Thomas Koenig wrote:
> Hi Paul,
>
>> Bootstraps and regtests on FC23/x86_64 - OK for trunk and 7 branch?
>
>
> OK for both. Thanks for the patc
On Fri, Sep 29, 2017 at 12:10:07PM -0500, Segher Boessenkool wrote:
> Hi Mike,
>
> On Thu, Sep 28, 2017 at 06:34:23PM -0400, Michael Meissner wrote:
> > This patch addss built-in functions on PowerPC ISA 3.0 (power9) that allow
> > the
> > user to access the round to odd IEEE 128-bit floating poi
On October 2, 2017 7:19:19 PM GMT+02:00, Martin Jambor wrote:
>Hi,
>
>the following fixes a thinko in propagate_subaccesses_across_link.
>When we cannot copy over a tree of accesses of RHS to LHS because of
>some conflict, we must mark the whole LHS access (sub-)tree as
>potentially written, even
On Thu, Sep 28, 2017 at 12:40:24AM +, Joseph Myers wrote:
> On Wed, 27 Sep 2017, Michael Meissner wrote:
>
> > The glibc team has requested we define the standard macro
> > (__FP_FAST_FMAF128)
> > for PowerPC code when we have the IEEE 128-bit floating point hardware
> > instructions enabled.
Hi,
the following fixes a thinko in propagate_subaccesses_across_link.
When we cannot copy over a tree of accesses of RHS to LHS because of
some conflict, we must mark the whole LHS access (sub-)tree as
potentially written, even when the RHS access describing this level is
not, because some of its
On Mon, Oct 02, 2017 at 12:00:55PM -0500, Peter Bergner wrote:
> On 9/29/17 5:31 PM, Segher Boessenkool wrote:
> >> +/* PowerPC 64-bit LE requires at least ISA 2.07. */
> >> +const char *default_cpu = ((!TARGET_POWERPC64)
> >> + ? "powerpc"
> >> +
On 9/29/17 5:31 PM, Segher Boessenkool wrote:
>> + /* PowerPC 64-bit LE requires at least ISA 2.07. */
>> + const char *default_cpu = ((!TARGET_POWERPC64)
>> + ? "powerpc"
>> + : ((BYTES_BIG_ENDIAN)
>> +
Jeff Law writes:
> @@ -468,6 +468,36 @@ maybe_trim_partially_dead_store (ao_ref *ref, sbitmap
> live, gimple *stmt)
> }
> }
>
> +/* Return TRUE if USE_REF reads bytes from LIVE where live is
> + derived from REF, a write reference.
> +
> + While this routine may modify USE_REF, it's p
On 10/02/2017 07:51 AM, Jakub Jelinek wrote:
> Hi!
>
> live_bytes is non-NULL always, m_live_bytes is auto_sbitmap that is
> constructed in dse_dom_walker ctor:
> dse_dom_walker (cdi_direction direction)
> : dom_walker (direction),
> m_live_bytes (PARAM_VALUE (PARAM_DSE_MAX_OBJECT_SIZE))
On October 2, 2017 3:51:04 PM GMT+02:00, Jakub Jelinek wrote:
>Hi!
>
>live_bytes is non-NULL always, m_live_bytes is auto_sbitmap that is
>constructed in dse_dom_walker ctor:
> dse_dom_walker (cdi_direction direction)
>: dom_walker (direction),
>m_live_bytes (PARAM_VALUE (PARAM_DSE_MAX_OB
On October 2, 2017 3:54:18 PM GMT+02:00, Jakub Jelinek wrote:
>Hi!
>
>On the following testcase we get a ref where
>ref->offset fits into shwi, so does ref->size, but ref->offset +
>ref->size
>doesn't. I see many spots where we just assume that ref->offset +
>ref->size
>is meaningful, so rather t
On Mon, Oct 2, 2017 at 4:58 AM, Richard Biener wrote:
>
> The following patch adjust GRAPHITE testing to check that existing
> code generation issues occur and makes code generation ICE with
> -fchecking --param graphite-allow-codegen-errors=0. The param
> is really a testsuite artifact so we can
On 29/09/17 21:29, Steve Ellcey wrote:
> On Thu, 2017-09-28 at 12:31 +0100, Szabolcs Nagy wrote:
>>
>> i think this should be improved, see below.
>
> Those were all good suggestions, here is a new patch that incorporates
> the changes. I fixed the IFUNC_OPTIONS argument,
> renamed ARCH_AARCH64
This adds the integral overloads of std::to_chars and std::from_chars,
including the changes made by P0682R0. Support for floating point types
is absent.
This uses a number of suggestions from Lars (thanks!) but I might have
missed some of his ideas and so could be missing some potential
optimiza
On Mon, Oct 02, 2017 at 01:32:01PM +0200, Jakub Jelinek wrote:
> On Mon, Oct 02, 2017 at 01:12:24PM +0200, Martin Liška wrote:
> > Hi.
> >
> > Currently I see with --with-build-config=bootstrap-ubsan:
> >
> > /home/marxin/BIG/buildbot/slave/gcc-master-bootstrap-ubsan/build/builddir/prev-x86_64-pc
Hi!
On the following testcase we get a ref where
ref->offset fits into shwi, so does ref->size, but ref->offset + ref->size
doesn't. I see many spots where we just assume that ref->offset + ref->size
is meaningful, so rather than adding overflow checking in all those spots,
this patch instead let
Hi!
live_bytes is non-NULL always, m_live_bytes is auto_sbitmap that is
constructed in dse_dom_walker ctor:
dse_dom_walker (cdi_direction direction)
: dom_walker (direction),
m_live_bytes (PARAM_VALUE (PARAM_DSE_MAX_OBJECT_SIZE)),
m_byte_tracking_enabled (false) {}
Whether live_bytes
Hi All,
The slp vectorization test currently fails on AArch32 and AArch64
due to it not taking into account that we do have 128 bit vectors in
NEON. This means that two of the loops get vectorized instead of just 1.
So update the conditions to include a check for neon.
Regtested on aarch64-none-
Hi All,
Previously I had corrected the vect_hw_misalign check which prompted these
three test to start failing because the condition needs to be inverted in the
testcases.
Regtested on aarch64-none-elf, arm-none-linux-gnueabihf and x86_64-pc-linux-gnu.
Ok for trunk?
Thanks,
Tamar.
gcc/testsuit
Hi!
On Fri, 22 Sep 2017 09:26:19 +0200 (CEST), Richard Biener
wrote:
> On Thu, 21 Sep 2017, Matthias Klose wrote:
> > On 21.09.2017 17:50, Ian Lance Taylor via gcc-patches wrote:
> > > On Thu, Sep 21, 2017 at 4:52 AM, Thomas Schwinge
> > > wrote:
> > >> I just happened to notice that contrib/gc
Hi!
On Mon, 02 Oct 2017 14:00:36 +0200, I wrote:
> On Thu, 28 Sep 2017 17:30:53 -0700, Ian Lance Taylor wrote:
> > This patch to libbacktrace adds support for compressed debug sections.
> > [...]
>
> > --- ztest.c (revision 0)
> > +++ ztest.c (working copy)
> > @@ -0,0 +1,446 @@
> > +/* ztest.c
Hi!
On Thu, 28 Sep 2017 17:30:53 -0700, Ian Lance Taylor wrote:
> This patch to libbacktrace adds support for compressed debug sections.
> [...]
> --- ztest.c (revision 0)
> +++ ztest.c (working copy)
> @@ -0,0 +1,446 @@
> +/* ztest.c -- Test for libbacktrace inflate code.
> +[...]
> +
On Mon, Oct 02, 2017 at 01:12:24PM +0200, Martin Liška wrote:
> Hi.
>
> Currently I see with --with-build-config=bootstrap-ubsan:
>
> /home/marxin/BIG/buildbot/slave/gcc-master-bootstrap-ubsan/build/builddir/prev-x86_64-pc-linux-gnu/libsanitizer/ubsan/.libs/libubsan.a(elf.o):
> In function `back
On Sun, Oct 01, 2017 at 09:22:56AM -0600, Jeff Law wrote:
>
> A short while ago Martin Liska posted a patch that lowered certain
> switch statements into cascading conditionals.
>
> His work tripped two regressions in the testsuite, both cases where we
> did not optimize as well as we should have
Hi.
Currently I see with --with-build-config=bootstrap-ubsan:
/home/marxin/BIG/buildbot/slave/gcc-master-bootstrap-ubsan/build/builddir/prev-x86_64-pc-linux-gnu/libsanitizer/ubsan/.libs/libubsan.a(elf.o):
In function `backtrace_uncompress_zdebug':
/home/marxin/BIG/buildbot/slave/gcc-master-boots
On Fri, Sep 29, 2017 at 08:42:45PM +, Joseph Myers wrote:
> On Fri, 29 Sep 2017, Joseph Myers wrote:
>
> > On Fri, 29 Sep 2017, Segher Boessenkool wrote:
> >
> > > How do other ports deal with this? Insns with a specific rounding mode?
> > > Have a separate unspec for every operation? Not v
The following patch adjust GRAPHITE testing to check that existing
code generation issues occur and makes code generation ICE with
-fchecking --param graphite-allow-codegen-errors=0. The param
is really a testsuite artifact so we can have testcases with
issues where we have papered over GRAPHITE
Changes since last patch are updating to version 2.076.
Phobos is the one part that could be arguably not strictly necessary,
as it is not tied to the compiler in any way, and is supposed to be
agnostic to any platform.
However it is typically expected that the compiler comes with this
library in
On Mon, Oct 2, 2017 at 6:53 AM, Sebastian Pop wrote:
> The patch moves the code that translates reads and writes to isl
> representation
> in a same loop. This is to avoid traversing the scop blocks and arrays with
> memory operations 3 times.
LGTM.
Richard.
> * graphite-dependences.c
Just updated copyright dates as per comments on previous revision, I
think everything should be in order.
---
diff --git a/libphobos/libdruntime/__entrypoint.di b/libphobos/libdruntime/__entrypoint.di
new file mode 100644
index 000..d04fe5d0889
--- /dev/null
+++ b/libphobos/libdruntime/__e
On Sun, Oct 1, 2017 at 6:13 PM, Richard Sandiford
wrote:
> The tree wi:: decompose routine wasn't asserting that the requested
> precision matched the tree's precision. This could make a difference
> for unsigned trees that are exactly N HWIs wide and that have the upper
> bit set, since we then
Changes since last patch are update to version 2.076.
As iterated before, these are maintained upstream, and are necessary
to link D applications.
Uploaded to ftp server due to size limitations.
Regards
Iain.
---
ftp://ftp.gdcproject.org/patches/v3/11-v3-d-runtime-library.patch.xz
libphobos/
Hi,
this patch requires effective target nonlocal_goto for
gcc.c-torture/compile/pr82337.c.
Committed.
Thanks,
- Tom
Require nonlocal_goto for gcc.c-torture/compile/pr82337.c
2017-10-02 Tom de Vries
* gcc.c-torture/compile/pr82337.c: Add
dg-require-effective-target nonlocal_goto.
---
This was split out from patch 9/14. Added test directories for ASAN
and LTO tests.
Regards
Iain.
---
diff --git a/gcc/testsuite/gdc.dg/asan/asan.exp b/gcc/testsuite/gdc.dg/asan/asan.exp
new file mode 100644
index 000..83bff4693e7
--- /dev/null
+++ b/gcc/testsuite/gdc.dg/asan/asan.exp
@@
Hi Richard
Thanks, I have made the change to the patch.
2017-10-02 Sudakshina Das
* config/aarch64/aarch64-protos.h (enum simd_immediate_check): New
check type
for aarch64_simd_valid_immediate.
(aarch64_output_simd_mov_immediate): Update prototype.
(aarch64_s
No changes from previous patch, just a refresh.
Mike, you don't need to look at this, just an FYI.
---
diff --git a/gcc/testsuite/gdc.test/d_do_test.exp b/gcc/testsuite/gdc.test/d_do_test.exp
new file mode 100644
index 000..4c03989443c
--- /dev/null
+++ b/gcc/testsuite/gdc.test/d_do_test.
Just added some more tests since previous patch for bug fixes made to
the D frontend.
Tests specific to GDC have also been removed also and put in a
separate directory with new dejagnu files.
I've uploaded the patch to my ftp server due to size limitations.
Regards
Iain
---
ftp://ftp.gdcprojec
This patch add D language support to targets of GCC itself.
Changes since previous are just removing patches for untested target
configurations, these can be re-added later on an as-per basis.
---
gcc/ChangeLog
* gcc/Makefile.in (tm_d_file_list, tm_d_include_list,
TM_D_H, D_TARGET_DEF, D_TARGE
No changes from previous, just rebased against trunk.
Regards
Iain
---
gcc/ChangeLog
* config/powerpcspe/powerpcspe.c (rs6000_output_function_epilogue):
Support GNU D by using 0 as the language type.
* config/rs6000/rs6000.c (rs6000_output_function_epilogue):
Support GNU D by using 0 as the
No change from the previous, just rebasing against trunk.
---
ChangeLog:
* Makefile.def (target_modules): Add libphobos.
(flags_to_pass): Add GDC_FOR_TARGET and GDCFLAGS_FOR_TARGET.
(dependencies): Add dependency from configure-target-libphobos to
configure-target-zlib. Add dependency from a
Updated changelogs following updates to patch 2/14.
Regards
Iain.
---
03-v3-d-frontend-changelogs.patch.xz
Description: application/xz
Changes since previous are just merge latest 2.076 release.
Uploaded patch to my ftp due to size limitations.
Regards
Iain.
---
ftp://ftp.gdcproject.org/patches/v3/01-v3-d-frontend-dmd.patch.xz
gcc/d/dfrontend/aav.c| 193 +
gcc/d/dfrontend/aav.h| 19 +
gcc/d/dfronte
On 11 September 2017 at 19:01, Jeff Law wrote:
> On 05/28/2017 03:47 PM, Iain Buclaw wrote:
>> This patch adds the D runtime library and license (Boost) files. D
>> runtime is a low level that implements the building blocks of the
>> runtime environment, as well as C and C++ platform bindings. M
> I have no idea how to do it. I opened:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82384
See Pierre-Marie's suggested patch on the PR.
Arno
73 matches
Mail list logo