Am 31.10.18 um 04:26 schrieb Joseph Myers:
This patch (diffs to generated files omitted below) updates GCC to use
autoconf 2.69 and automake 1.15.1.
I think this should fix PR 82856. Maybe you could confirm that this
restores automake functionality with perl 5.6.26, and mention the PR
in the C
On Wed, 31 Oct 2018 at 00:37, James Greenhalgh wrote:
>
> On Tue, Oct 30, 2018 at 05:12:58AM -0500, Sameera Deshpande wrote:
> > On Fri, 26 Oct 2018 at 13:33, Sameera Deshpande
> > wrote:
> > >
> > > Hi!
> > >
> > > Please find attached the patch to add a pipeline description for the
> > > Qualco
On Wed, 31 Oct 2018 at 05:38, Alan Modra wrote:
>
> On Tue, Oct 30, 2018 at 09:07:30PM +0100, Iain Buclaw wrote:
> > On Tue, 30 Oct 2018 at 20:50, Andreas Schwab wrote:
> > >
> > > On Okt 30 2018, Iain Buclaw wrote:
> > >
> > > > This turns off D front-end where there's been reported bootstrap
>
Thank you for your review. Please find attached a new respin patch with
your feedback in.
Please let me know if it is ok,
Claudiu
From 4ff7d8419783eceeffbaf27df017d0a93c3af942 Mon Sep 17 00:00:00 2001
From: Claudiu Zissulescu
Date: Thu, 9 Aug 2018 14:29:05 +0300
Subject: [PATCH] [ARC] Add peepho
On Wed, Oct 31, 2018 at 9:12 AM Thomas Koenig wrote:
> > Makefile.am:48: warning: source file 'caf/single.c' is in a subdirectory,
> > Makefile.am:48: but option 'subdir-objects' is disabled
> > automake: warning: possible forward-incompatibility.
> > automake: At least a source file is in a subd
> I'm not a fan of this approach. I'd rather the comment explain what
> problem was found and patched, and why displaying a warning is not
> appropriate. The commented out code just leaves me asking ... why?
>
Having the warning here breaks a number of builds, like the linux
kernel build. On
Committed.
Richard.
2018-10-31 Richard Biener
PR testsuite/87802
* g++.dg/vect/slp-pr87105.cc: XFAIL for strict alignment targets.
Index: gcc/testsuite/g++.dg/vect/slp-pr87105.cc
===
--- gcc/testsuite/g++.dg/ve
On Wed, Oct 31, 2018 at 7:27 AM bin.cheng wrote:
>
> Hi,
> This simple patch avoids infinite recursion when tracing inlined function
> decl by using
> pre-defined macro DECL_FROM_INLINE in tree.h.
>
> Bootstrap and test on x86_64 in patch set. Is it OK?
OK.
Richard.
> Thanks,
> bin
>
> 2018-1
On Mon, Oct 29, 2018 at 05:00:36PM +0100, Jakub Jelinek wrote:
> On Mon, Oct 29, 2018 at 10:38:11AM -0500, Bill Seurer wrote:
> > > I'm still wondering what didn't work with 41 bits? AFAICS, due to
> > > highshadow=highmem-offset and lowshadow=low+offset, and the existence of a
> > > non-empty sha
On Wed, Oct 31, 2018 at 7:30 AM bin.cheng wrote:
>
> Hi,
> In new profile probability/count infra, we have different precision quality
> categories,
> and probabilities/counts of different categories are not supposed to be
> compared or
> calculated. Though in general is an improvement, it intr
On Wed, Oct 31, 2018 at 7:31 AM bin.cheng wrote:
>
> Hi,
> This is a simple patch setting profile_count with according precision
> category in
> AutoFDO, as well as setting profile_count for exit basic block.
>
> Bootstrap and test on x86_64 in patch set. Is it OK?
OK. It might look cleaner (a
On Tue, Oct 30, 2018 at 8:25 PM Iain Buclaw wrote:
>
> Hi,
>
> This turns off D front-end where there's been reported bootstrap
> problems that need further investigation. Also added a configure.tgt
> for libphobos to allow enabling for targets where there's known good
> runtime support backed by
On Wed, Oct 31, 2018 at 5:11 PM Richard Biener
wrote:
>
> On Wed, Oct 31, 2018 at 7:30 AM bin.cheng wrote:
> >
> > Hi,
> > In new profile probability/count infra, we have different precision quality
> > categories,
> > and probabilities/counts of different categories are not supposed to be
> >
On Tue, Oct 30, 2018 at 11:07:16AM +0100, Martin Li??ka wrote:
> On 10/29/18 12:04 PM, Martin Li??ka wrote:
> > 2) gfc_find_module
> >
> > $ ./xgcc -B.
> > /home/marxin/Programming/gcc/gcc/testsuite/gfortran.dg/coarray/alloc_comp_2.f90
> > -fcoarray=single -fchecking=3
> > hash table checking fa
Hi Iain,
> My first suspect here would be 'struct UnionExp', see d/dmd/expression.h
>
> Upstream dmd use a poor man's alignment, from what I recall to be
> compatible with the dmc compiler.
>
> // Ensure that the union is suitably aligned.
> real_t for_alignment_only;
>
> What happ
Hi Iain,
>> My first suspect here would be 'struct UnionExp', see d/dmd/expression.h
>>
>> Upstream dmd use a poor man's alignment, from what I recall to be
>> compatible with the dmc compiler.
>>
>> // Ensure that the union is suitably aligned.
>> real_t for_alignment_only;
>>
>>
On Wed, Oct 31, 2018 at 8:12 AM Thomas Koenig wrote:
>
> Am 31.10.18 um 04:26 schrieb Joseph Myers:
> > This patch (diffs to generated files omitted below) updates GCC to use
> > autoconf 2.69 and automake 1.15.1.
>
> I think this should fix PR 82856. Maybe you could confirm that this
> restores
On Wed, Oct 31, 2018 at 4:26 AM Joseph Myers wrote:
>
> This patch (diffs to generated files omitted below) updates GCC to use
> autoconf 2.69 and automake 1.15.1. (That's not the latest automake
> version, but it's the one used by binutils-gdb, with which consistency
> is desirable, and in any c
On 10/31/18 10:40 AM, Trevor Saunders wrote:
> On Tue, Oct 30, 2018 at 11:07:16AM +0100, Martin Li??ka wrote:
>> On 10/29/18 12:04 PM, Martin Li??ka wrote:
>>> 2) gfc_find_module
>>>
>>> $ ./xgcc -B.
>>> /home/marxin/Programming/gcc/gcc/testsuite/gfortran.dg/coarray/alloc_comp_2.f90
>>> -fcoarray
Ilya Leoshkevich wrote:
> Am 30.10.2018 um 18:22 schrieb Ulrich Weigand :
> > This definitely looks wrong. If we haven't annotated the address,
> > it should *not* be found by find_constant_pool_ref, since we are
> > not going to replace it! That was the whole point of not annotating
> > it in th
Hello.
This is a regression that was introduced in r216127.
I tested the patch on ppc64le and I'm going to install it.
Martin
gcc/fortran/ChangeLog:
2018-10-30 Martin Liska
* trans-decl.c (struct module_hasher): Call htab_hash_string
for s->name and not for s.
---
gcc/fortr
On 10/30/18 7:48 PM, James Greenhalgh wrote:
> On Tue, Oct 02, 2018 at 11:19:05AM -0500, Richard Henderson wrote:
>> The cas insn is a single insn, and if expanded properly need not
>> be split after reload. Use the proper inputs for the insn.
>
> OK.
Thanks. Committed 1-4 & 9.
r~
Hi.
As Jakub pointed out we should not ICE when last argument
of __builtin_expect_with_probability is not a real cst.
Plus I documented the behavior.
Patch survives regression tests on x86_64-linux-gnu and
bootstraps works fine.
Ready for trunk?
Thanks,
Martin
gcc/ChangeLog:
2018-10-30 Martin
On 10/30/18 8:32 PM, James Greenhalgh wrote:
> On Tue, Oct 02, 2018 at 11:19:09AM -0500, Richard Henderson wrote:
>> When the result of an operation is not used, we can ignore the
>> result by storing to XZR. For two of the memory models, using
>> XZR with LD has a preferred assembler alias, ST.
>
On Wed, Oct 31, 2018 at 11:04:32AM +0100, Martin Liška wrote:
> Hi.
>
> As Jakub pointed out we should not ICE when last argument
> of __builtin_expect_with_probability is not a real cst.
> Plus I documented the behavior.
That is not what you've implemented. The documentation says that
it must b
On 10/30/18 8:32 PM, James Greenhalgh wrote:
> On Tue, Oct 02, 2018 at 11:19:09AM -0500, Richard Henderson wrote:
>> When the result of an operation is not used, we can ignore the
>> result by storing to XZR. For two of the memory models, using
>> XZR with LD has a preferred assembler alias, ST.
>
Ping for rtl, middle-end, or global reviewers.
r~
On 10/2/18 5:19 PM, Richard Henderson wrote:
> * optabs-libfuncs.c (build_libfunc_function_visibility):
> New, split out from...
> (build_libfunc_function): ... here.
> (init_one_libfunc_visibility): New, split out from ..
Hi Martin,
> libsanitizer/ChangeLog:
>
> 2018-10-24 Martin Liska
>
> * config.h.in: Regenerate.
> * configure: Likewise.
> * sanitizer_common/Makefile.am: Include new files, remove old
> files.
> * sanitizer_common/Makefile.in: Regenerate.
I noticed that this patc
On 10/31/18 11:35 AM, Rainer Orth wrote:
> Hi Martin,
>
>> libsanitizer/ChangeLog:
>>
>> 2018-10-24 Martin Liska
>>
>> * config.h.in: Regenerate.
>> * configure: Likewise.
>> * sanitizer_common/Makefile.am: Include new files, remove old
>> files.
>> * sanitizer_common/M
Hi all,
The patch adds a check if the gap is compile-time constant.
This happens when dse decides to replace the load with previous store value.
The problem is that, shift sequence could not accept compile-time non-constant
mode operand.
Another issue raised from this issue is the inefficient c
Hi.
I install the patch set. If I'm correct one last missing piece should
be update of LOCAL_PATCHES. I'm sending patch for it.
Ready for trunk?
Thanks,
Martin
>From 02134e26743eed447f62f7e22d75ddfe605e88e3 Mon Sep 17 00:00:00 2001
From: marxin
Date: Wed, 31 Oct 2018 12:22:36 +0100
Subject: [PAT
On Wed, Oct 31, 2018 at 12:24:47PM +0100, Martin Liška wrote:
> I install the patch set. If I'm correct one last missing piece should
> be update of LOCAL_PATCHES. I'm sending patch for it.
Ok, thanks.
Jakub
Thank you all for your review. The patch is pushed with your input in.
//Claudiu
Committed with your feedback in. Thank you,
Claudiu
Thank you for your review. Patch pushed,
Claudiu
Committed with your feedback in. Thank you,
Claudiu
Committed with feedback in. Thank you,
Claudiu
On Tue, 30 Oct 2018, Richard Biener wrote:
>
> This picks up work from earlier this year where Aldy worked on
> undoing forwprop during out-of-SSA to improve coalescing across
> backedges.
>
> The following patch first rectifies the existing code which
> is meant to insert necessary copies in pl
The introduction of the empty __pair_base base class for PR 86751
changed the layout of std::pair, ...>. The outer pair and
its first member both have a base class of the same type, which cannot
exist at the same address. This causes the first member to be at a
non-zero offset.
The solution is to
When I redid namespace-scope name lookup I made overload sets ordered
hidden, then using, then other. This was with an eye to how modules
would need to extend that to add 'exported' on the end. Turns out
that's not needed, so we can simplify a bit. This patch changes things
so that using and
On 31/10/18 12:31 +, Jonathan Wakely wrote:
The introduction of the empty __pair_base base class for PR 86751
changed the layout of std::pair, ...>. The outer pair and
its first member both have a base class of the same type, which cannot
exist at the same address. This causes the first membe
Honza reports high CPU usage from lookup_external_ref at LTRANS time.
This is likely because build_abbrev_table calls it on all DIEs
rather than just type DIEs which we populate the ref table with.
So we end up calling it for all the DIEs refering to early debug,
possibly many distinct ones with
On Tue, Oct 30, 2018 at 8:26 PM, Joseph Myers wrote:
>
> This patch (diffs to generated files omitted below) updates GCC to use
> autoconf 2.69 and automake 1.15.1. (That's not the latest automake
> version, but it's the one used by binutils-gdb, with which consistency
> is desirable, and in any
I'm committing this addition to the release notes as part of my public
shaming.
Index: htdocs/gcc-6/changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-6/changes.html,v
retrieving revision 1.110
retrieving revision 1.111
diff -u
On 2018-10-30 11:26 p.m., Joseph Myers wrote:
> This patch (diffs to generated files omitted below) updates GCC to use
> autoconf 2.69 and automake 1.15.1. (That's not the latest automake
> version, but it's the one used by binutils-gdb, with which consistency
> is desirable, and in any case seems
Thanks for the feedback. I made some improvements.
Changes from the first patch:
config.gcc:
need_64bit_hwint=yes No longer needed
resolve conflict from strongarm being default for netbsd.
switch default cpu for armv7--netbsdelf-eabi: cortex-a8 -> generic-armv7-a,
(make -mfpu=auto pick VFPv3-D16)
The following fixes a thinko in the rpo-vn-max-loop-depth param handling.
Bootstrapped and tested on x86_64-unknown-linux-gnu.
Richard.
>From 172251b9fdd1ace4c18fb9308be3f4f3ed868241 Mon Sep 17 00:00:00 2001
From: Richard Guenther
Date: Wed, 31 Oct 2018 13:33:21 +0100
Subject: [PATCH] fix-pr8
On 10/30/18 10:46 PM, Jan Hubicka wrote:
> Hi,
> this patch increases lto-partitions to 128. This makes ltrans.o file sizes to
> grow from 458MB to 651MB which is still not perfect but a lot better than
> prevoiusly. On firefox the growth is smaller (only about 10%) which is
> probably caused by
On 10/31/18 12:30 AM, bin.cheng wrote:
> Hi,
> In new profile probability/count infra, we have different precision quality
> categories,
> and probabilities/counts of different categories are not supposed to be
> compared or
> calculated. Though in general is an improvement, it introduces unexpe
On 10/30/18 4:35 PM, Stafford Horne wrote:
> On Tue, Oct 30, 2018 at 10:49:53AM -0500, Segher Boessenkool wrote:
>> On Tue, Oct 30, 2018 at 09:49:18PM +0900, Stafford Horne wrote:
>>> Hello,
>>>
>>> On Sun, Oct 28, 2018 at 05:54:47PM -0500, Segher Boessenkool wrote:
Yes, like that. It also ea
This is patch 1 of 7 from the modules branch, cleaning up random
preprocessor stuff I fell over.
The directive table has some historical frequency data, which was
relevant when we used to have to do a lookup for the directives. Now
the data hangs directly off the identifier node.
A minor in
The hashnode identifier accessor macro unnecessarily casts its operand,
and the derived accessors don't use it. Fixed thusly.
applying to trunk.
--
Nathan Sidwell
2018-10-31 Nathan Sidwell
* include/cpplib.h (HT_NODE): Don't cast NODE.
(NODE_LEN, NODE_NAME): Use HT_NODE.
Index: libcpp/i
Now that the cpp_macro structure is properly part of cpplib.h, we don't
need to outline its location accessor function. Made inline thusly.
Cleaned up duplicate macro checking a bit too.
applying to trunk
nathan
--
Nathan Sidwell
2018-10-31 Nathan Sidwell
* include/cpplib.h (cpp_macro_d
This fills out the set of location-kind predicates, and uses them in a
couple more places. There may well be other places that could benefit.
Applying to trunk.
--
Nathan Sidwell
2018-10-31 Nathan Sidwell
* include/line-map.h (IS_ORDINARY_LOC, IS_MACRO_LOC): New
predicates.
(IS_ADHOC_LO
[Yes, I can't count]
Include file handling duplicated cleanup code in each exit path.
Simpler to just commonize it with goto. Also noticed a memory leak in
buffer popping.
Applying to trunk.
--
Nathan Sidwell
2018-10-31 Nathan Sidwell
* directives.c (do_include_common): Commonize clea
Hi Richard,
On Wed, Oct 31, 2018 at 10:27:59AM +, Richard Henderson wrote:
> On 10/30/18 8:32 PM, James Greenhalgh wrote:
> > On Tue, Oct 02, 2018 at 11:19:09AM -0500, Richard Henderson wrote:
> >> When the result of an operation is not used, we can ignore the
> >> result by storing to XZR. F
On 31/10/2018 14:10, co...@sdf.org wrote:
> +
> +# Currently there is a bug somewhere in GCC's alias analysis
> +# or scheduling code that is breaking _fpmul_parts in fp-bit.c.
> +# Disabling function inlining is a workaround for this problem.
> +HOST_LIBGCC2_CFLAGS += -fno-inline
This needs to be
There's an API for forcing all macro definition token positions to be X.
That takes a pointer to X, so one can distinguish between not forcing
a location, and forcing the location to be UNKNOWN_LOCATION.
However, we only use this to force BUILTINS_LOCATION, and if you're
forcing UNKNOWN_LOCAT
I observed the odd looking code while looking into something else and confirmed
prior behavior (before r248863) was to sum the counts of the non-latch
predecessors of the loop (in order to scale the loop such that it no longer
appears to iterate).
Bootstrap/regtest on powerpc64le with no regres
On Mon, 15 Oct 2018, Richard Biener wrote:
> I think it's sound but also note that I think it is logically independent of
> asm inline (). While it may work for the inlining issue for some kernel
> examples to asm inline () is sth similar to always_inline for functions,
> that is, even though an a
On Wed, Oct 31, 2018 at 11:02:16AM -0400, Nathan Sidwell wrote:
> [Yes, I can't count]
>
> Include file handling duplicated cleanup code in each exit path. Simpler to
> just commonize it with goto. Also noticed a memory leak in buffer popping.
>
> Applying to trunk.
>
> --
> Nathan Sidwell
>
>
> Honza reports high CPU usage from lookup_external_ref at LTRANS time.
> This is likely because build_abbrev_table calls it on all DIEs
> rather than just type DIEs which we populate the ref table with.
> So we end up calling it for all the DIEs refering to early debug,
> possibly many distinct
Ping. The latest patch is here:
https://gcc.gnu.org/ml/gcc-patches/2018-10/msg01551.html
On 10/24/2018 08:02 PM, Martin Sebor wrote:
On 10/16/2018 04:35 PM, Jeff Law wrote:
On 10/8/18 5:22 PM, Martin Sebor wrote:
Attached is an updated patch with the INTEGRAL_TYPE_P test added
to detect con
Ping: https://gcc.gnu.org/ml/gcc-patches/2018-10/msg01481.html
There was quite a bit of discussion between Joseph and me about
the Glibc changes needed to take advantage of the solution but
the GCC patch itself (above) still needs reviewing/approval.
Other than some (minor) changes to the C++ fr
On 10/31/18 11:44 AM, Marek Polacek wrote:
+ else if (to_free)
+free ((void *)to_free);
free (NULL) is ok so do you really need the check?
Probably not :) IIRC the if (X) free (X) idiom was nearby, and I didn't
feel like rocking that boat.
nathan
--
Nathan Sidwell
Ping: https://gcc.gnu.org/ml/gcc-patches/2018-10/msg01473.html
With the C++ bits approved I'm still looking for a review/approval
of the remaining changes: the C front end and the shared c-family
handling of the new built-in.
On 10/23/2018 04:08 PM, Martin Sebor wrote:
On 10/22/2018 04:08 PM, J
On Wed, Oct 31, 2018 at 12:24:44PM -0400, Nathan Sidwell wrote:
> On 10/31/18 11:44 AM, Marek Polacek wrote:
>
> > > + else if (to_free)
> > > +free ((void *)to_free);
> >
> > free (NULL) is ok so do you really need the check?
>
> Probably not :) IIRC the if (X) free (X) idiom was nearby,
On 10/25/2018 09:40 PM, Joseph Myers wrote:
On Thu, 25 Oct 2018, Rajalakshmi Srinivasaraghavan wrote:
+ if (__builtin_unpack_longdouble (a, 0) < TWO53)
+{
+ /* In this case the integer portion is completely contained
+ within the high double. So use the hardware convert to
Ping: https://gcc.gnu.org/ml/gcc-patches/2018-08/msg01818.html
On 10/20/2018 06:01 PM, Martin Sebor wrote:
On 10/16/2018 03:21 PM, Jeff Law wrote:
On 10/4/18 9:51 AM, Martin Sebor wrote:
On 10/04/2018 08:58 AM, Jeff Law wrote:
On 8/27/18 9:42 AM, Richard Biener wrote:
On Mon, Aug 27, 2018 at
Ping: https://gcc.gnu.org/ml/gcc-patches/2018-08/msg01934.html
On 10/08/2018 03:40 PM, Martin Sebor wrote:
Ping: https://gcc.gnu.org/ml/gcc-patches/2018-08/msg01934.html
On 10/01/2018 03:30 PM, Martin Sebor wrote:
Ping: https://gcc.gnu.org/ml/gcc-patches/2018-08/msg01934.html
We have discusse
On 10/30/18, Joseph Myers wrote:
> This patch (diffs to generated files omitted below) updates GCC to use
> autoconf 2.69 and automake 1.15.1. (That's not the latest automake
> version, but it's the one used by binutils-gdb, with which consistency
> is desirable, and in any case seems a useful in
Hi.
As seen in r265663 having htab_hash_string accepting const char * would
report a compilation error. The void * argument is needed for old C-style
htab used in libiberty. I'm suggesting to come up with htab_hash_string_vptr and
change signature of the old one (htab_hash_string). And putting the
On Wed, 31 Oct 2018 at 10:40, Rainer Orth wrote:
>
> Hi Iain,
>
> > My first suspect here would be 'struct UnionExp', see d/dmd/expression.h
> >
> > Upstream dmd use a poor man's alignment, from what I recall to be
> > compatible with the dmc compiler.
> >
> > // Ensure that the union is s
On Wed, 31 Oct 2018, Thomas Koenig wrote:
> Am 31.10.18 um 04:26 schrieb Joseph Myers:
> > This patch (diffs to generated files omitted below) updates GCC to use
> > autoconf 2.69 and automake 1.15.1.
>
> I think this should fix PR 82856. Maybe you could confirm that this
> restores automake fun
On 10/31/18 3:04 PM, Will Deacon wrote:
> The example test above uses relaxed atomics in conjunction with an acquire
> fence, so I don't think we can actually use ST at all without a change
> to the language specification. I previouslyyallocated P0861 for this purpose
> but never got a chance to wr
The processing of command line macros is a little confusing. In the
same way we force builtin locations, we should force command line
locations. We also call the main-starting debug hook on two separate
paths. I found it clearer to call it once, and then restart the
non-preprocessed handling
On Wed, 31 Oct 2018, Simon Marchi wrote:
> On 2018-10-30 11:26 p.m., Joseph Myers wrote:
> > This patch (diffs to generated files omitted below) updates GCC to use
> > autoconf 2.69 and automake 1.15.1. (That's not the latest automake
> > version, but it's the one used by binutils-gdb, with which
> * optabs-libfuncs.c (build_libfunc_function_visibility):
> New, split out from...
> (build_libfunc_function): ... here.
> (init_one_libfunc_visibility): New, split out from ...
> (init_one_libfunc): ... here.
Either that or add the parameter with a VISIBILITY_DEFAUL
I missed committing this testcase with the recent unsorted overload change.
nathan
--
Nathan Sidwell
2018-10-31 Nathan Sidwell
* g++.dg/lookup/friend21.C: New.
Index: testsuite/g++.dg/lookup/friend21.C
===
--- testsuite/g++.dg/
On Wed, 31 Oct 2018 at 10:43, Rainer Orth wrote:
>
> Hi Iain,
>
> >> My first suspect here would be 'struct UnionExp', see d/dmd/expression.h
> >>
> >> Upstream dmd use a poor man's alignment, from what I recall to be
> >> compatible with the dmc compiler.
> >>
> >> // Ensure that the unio
Here is the updated patch.
I forgot that pre-C+11 we already had the default copy constructor and
assignment operators. And with the trick on definition of _M_start the
patch is much smaller.
* include/bits/stl_bvector.h
[_GLIBCXX_INLINE_VERSION](_Bvector_impl_data::_M_start): Define
On Wed, 31 Oct 2018, Rajalakshmi Srinivasaraghavan wrote:
> On 10/25/2018 09:40 PM, Joseph Myers wrote:
> > On Thu, 25 Oct 2018, Rajalakshmi Srinivasaraghavan wrote:
> >
> > > + if (__builtin_unpack_longdouble (a, 0) < TWO53)
> > > +{
> > > + /* In this case the integer portion is compl
On Wed, 31 Oct 2018, Eric Gallager wrote:
> > Index: zlib/Makefile.am
> > ===
> > --- zlib/Makefile.am(revision 265631)
> > +++ zlib/Makefile.am(working copy)
> > @@ -1,6 +1,6 @@
> > ## Process this file with automake
On 10/31/18 5:32 PM, Eric Botcazou wrote:
>> * optabs-libfuncs.c (build_libfunc_function_visibility):
>> New, split out from...
>> (build_libfunc_function): ... here.
>> (init_one_libfunc_visibility): New, split out from ...
>> (init_one_libfunc): ... here.
>
> Either that
On 10/31/18, Marek Polacek wrote:
> On Wed, Oct 31, 2018 at 11:02:16AM -0400, Nathan Sidwell wrote:
>> [Yes, I can't count]
>>
>> Include file handling duplicated cleanup code in each exit path. Simpler
>> to
>> just commonize it with goto. Also noticed a memory leak in buffer
>> popping.
>>
>>
On Wed, Oct 31, 2018 at 04:38:53PM +, Richard Henderson wrote:
> On 10/31/18 3:04 PM, Will Deacon wrote:
> > The example test above uses relaxed atomics in conjunction with an acquire
> > fence, so I don't think we can actually use ST at all without a change
> > to the language specification. I
> I thought of that, but thought this was slightly clearer from usage. I'm
> open the default option if you prefer.
No, either is fine as far as I'm concerned.
--
Eric Botcazou
Sorry for the slow reply. I've been stuck working on some other projects.
> Can you say a bit about why that was better than continuing to use
> VAR_DECL?
>
I wanted to make sure that we avoid normal VAR_DECL processing routines, so
we don't e.g., slip into a function where we might try to gener
Hi,
I just committed the test case below so the bug can be closed.
The error message is less than ideal, but at least it is something.
Maybe I'll file a separate PR about translating error messages about
artificial variables to user's variables.
Regards
Thomas
2018-10-31 Thomas Koeni
I fell over this on the modules branch, first with simplifying our
internal structures, and then finding a bug.
Local entities can need a discriminator in their mangling. We didn't
always get that right.
Firstly, we rarely need a discriminator, and a non-zero one is even
rarer. So there's
Hi Iain,
> This turns off D front-end where there's been reported bootstrap
> problems that need further investigation. Also added a configure.tgt
> for libphobos to allow enabling for targets where there's known good
> runtime support backed by existing continuous integration.
>
> For both, this
Hi Iain
> On 31 Oct 2018, at 19:35, Rainer Orth wrote:
>
> Hi Iain,
>
>> This turns off D front-end where there's been reported bootstrap
>> problems that need further investigation. Also added a configure.tgt
>> for libphobos to allow enabling for targets where there's known good
>> runtime s
On Thu, Sep 27, 2018 at 7:58 AM Richard Biener
wrote:
>
> On Thu, Sep 27, 2018 at 3:16 PM H.J. Lu wrote:
> >
> > On Thu, Sep 27, 2018 at 6:08 AM, Szabolcs Nagy
> > wrote:
> > > On 26/09/18 19:10, H.J. Lu wrote:
> > >>
> > >> Add -mzero-caller-saved-regs=[skip|used|all] command-line option and
>
On Wed, Oct 31, 2018 at 10:04 AM, Joseph Myers wrote:
> On Wed, 31 Oct 2018, Thomas Koenig wrote:
>
>> Am 31.10.18 um 04:26 schrieb Joseph Myers:
>> > This patch (diffs to generated files omitted below) updates GCC to use
>> > autoconf 2.69 and automake 1.15.1.
>>
>> I think this should fix PR 828
On 10/30/2018 04:34 PM, Joseph Myers wrote:
On Tue, 30 Oct 2018, Martin Sebor wrote:
So it seems that the attribute handler should be using this macro
instead. I also took the liberty to add more detail to the error
Note that it should only be used for alignments relevant to the object
file
Hi,
This fixes build for profiledbootstrap when D is enabled. Commited as obvious.
--
Iain
---
gcc/d/ChangeLog:
2018-10-31 Iain Buclaw
PR d/87825
* Make-lang.in (d/idgen) Link with BUILD_LINKERFLAGS.
(d/impcvgen): Likewise.
---
diff --git a/gcc/d/Make-lang.in b/gcc/d/Make-lang
On 31.10.18 05:37, Alan Modra wrote:
> On Tue, Oct 30, 2018 at 09:07:30PM +0100, Iain Buclaw wrote:
>> On Tue, 30 Oct 2018 at 20:50, Andreas Schwab wrote:
>>>
>>> On Okt 30 2018, Iain Buclaw wrote:
>>>
This turns off D front-end where there's been reported bootstrap
problems that need f
On 10/31/18 5:51 PM, Will Deacon wrote:
> Aha, maybe this is the problem. An acquire fence on AArch64 is implemented
> using a DMB LD instruction, which orders prior reads against subsequent
> reads and writes. However, the architecture says:
>
> | The ST instructions, and LD instructions where
On Wed, 31 Oct 2018, Iain Sandoe wrote:
> maybe if building D .. then libphobos should be automatic
> (i.e. the opt-in/out for the targets under development is to choose to
> build/not build D explicitly)?
>
> [ that would avoid having to have the UNSUPPORTED stuff in the
> libphobos/config.tg
On Wed, Oct 31, 2018 at 03:23:27PM +, Richard Earnshaw (lists) wrote:
> On 31/10/2018 14:10, co...@sdf.org wrote:
> > +
> > +# Currently there is a bug somewhere in GCC's alias analysis
> > +# or scheduling code that is breaking _fpmul_parts in fp-bit.c.
> > +# Disabling function inlining is a
1 - 100 of 111 matches
Mail list logo
