On Fri, Jul 17, 2020 at 1:22 AM Richard Biener
wrote:
>
> On Fri, Jul 17, 2020 at 7:15 AM Sunil Pandey wrote:
> >
> > Any comment on revised patch? At least, in finish_decl, decl global
> > attributes are populated.
>
> +static void
> +ix86_lower_local_decl_alignment (tree decl)
> +{
> + unsig
Committed as obvious. Gets rid of a spurious failure for mmix.
gcc/testsuite:
* c-c++-common/cpp/pragma-eof.c: Require fopenmp.
diff --git a/gcc/testsuite/c-c++-common/cpp/pragma-eof.c
b/gcc/testsuite/c-c++-common/cpp/pragma-eof.c
index c72be80..9537470 100644
--- a/gcc/testsuite/c-c++-
On 7/17/20 5:07 PM, Peter Bergner wrote:
> As we discussed offline, we need the duplicated constraint alternatives
> like below. I'll test this and commit this if clean with the following
> additional ChangeLog entry for the p9 addition. Thanks.
Testing was clean, so I pushed the commit. Thanks
On 7/17/20 4:32 PM, Segher Boessenkool wrote:
> Well, just make an "isa" value of "p9"? Then you can just do
>
> (define_insn "trunctdsd2"
> [(set (match_operand:SD 0 "gpc_reg_operand" "=d")
> (float_truncate:SD (match_operand:TD 1 "gpc_reg_operand" "d")))
>(clobber (match_scratch:T
On Fri, Jul 17, 2020 at 04:18:55PM -0500, Peter Bergner wrote:
> On 7/17/20 3:23 PM, Segher Boessenkool wrote:
> > On ISA 3.0B and later you can do
> >
> > mffscdrni %3,7
> > drdpq %2,%1
> > mffscdrn %3,%3
> > drsp %0,%2
> >
> > (saving one insn, and using somewhat cheaper insns).
This patch to libgo updates it to the Go 1.14.6 release. Bootstrapped
and ran Go testsuite on x86_64-pc-linux-gnu. Committed to mainline.
Ian
patch.txt.bz2
Description: application/bzip
On 7/17/20 3:23 PM, Segher Boessenkool wrote:
> On ISA 3.0B and later you can do
>
> mffscdrni %3,7
> drdpq %2,%1
> mffscdrn %3,%3
> drsp %0,%2
>
> (saving one insn, and using somewhat cheaper insns). But that is only
> on newer machines, so is this worth it at all? :-)
On Fri, Jul 17, 2020 at 02:47:50PM -0500, Peter Bergner wrote:
> PR92488 shows we do not generate hardware conversion instructions when
> converting from _Decimal128 to _Decimal32. There is no one instruction
> that does the conversion, so we currently call the __dpd_trunctdsd2
> function to do th
PR92488 shows we do not generate hardware conversion instructions when
converting from _Decimal128 to _Decimal32. There is no one instruction
that does the conversion, so we currently call the __dpd_trunctdsd2
function to do the conversion for us. This is slow. Paul Murphy
described a short sequ
The recent enhancement to treat the implicit this pointer argument
as nonnull in member functions triggers spurious -Wnonnull for
the synthesized conditional expression the C++ front end replaces
the pointer with in some static_cast expressions. The front end
already sets the no-warning bit for t
On Fri, 17 Jul 2020, Patrick Palka wrote:
> On Wed, 15 Jul 2020, Patrick Palka wrote:
>
> > On Tue, 14 Jul 2020, Patrick Palka wrote:
> >
> > > This implements the floating-point std::to_chars overloads for float,
> > > double and long double. We use the Ryu library to compute the shortest
> >
On 7/13/20 4:48 PM, Marek Polacek wrote:
On Sat, Jul 11, 2020 at 10:32:55AM -0400, Jason Merrill via Gcc-patches wrote:
On 7/8/20 4:35 PM, Marek Polacek wrote:
On Fri, Jul 03, 2020 at 05:24:34PM -0400, Jason Merrill via Gcc-patches wrote:
On 6/22/20 10:09 PM, Marek Polacek wrote:
convert_like
On 7/8/20 10:48 PM, Marek Polacek wrote:
"If the placeholder is the decltype(auto) type-specifier, T shall be the
placeholder alone." but we weren't detecting "const decltype(auto)".
I've just expanded the existing diagnostic detecting "decltype(auto) &"
and similar.
Bootstrapped/regtested on x
Sounds good to me! Don't think I'd be qualified or have the know how
to make this change but the testsuite above should hopefully be of
use.
On Fri, Jul 17, 2020 at 3:59 PM Jan Hubicka wrote:
>
> > Yes that is correct. GCC simply checks if a symbol is part of a comdat
> > group and if it is, emit
> Yes that is correct. GCC simply checks if a symbol is part of a comdat
> group and if it is, emits .linkonce for it's section. GAS then sees
> the directive and moves the symbol corresponding to the section name
> to be the first symbol so it becomes the key. See:
> https://github.com/bminor/binu
On Fri, Jul 17, 2020 at 6:27 AM Richard Biener wrote:
>
> On Fri, 17 Jul 2020, H.J. Lu wrote:
>
> > On Fri, Jul 17, 2020 at 12:08 AM Richard Biener wrote:
> > >
> > > On Wed, 15 Jul 2020, Joseph Myers wrote:
> > >
> > > > On Wed, 15 Jul 2020, Richard Biener wrote:
> > > >
> > > > > But note one o
Sorry for the late review. I hope you're still willing to work on
this!
On 02/01/20 17:16 -0500, JeanHeyd Meneide wrote:
Glen Fernandes is already working on a patch, so I decided to finish
off my changes and throw them up on the Patch List so that Glen can
access the tests parts that I had wri
On Fri, 17 Jul 2020, H.J. Lu wrote:
> On Fri, Jul 17, 2020 at 12:08 AM Richard Biener wrote:
> >
> > On Wed, 15 Jul 2020, Joseph Myers wrote:
> >
> > > On Wed, 15 Jul 2020, Richard Biener wrote:
> > >
> > > > But note one of the issues is that when not cross-compiling we're
> > > > using a single
Thank you!
On 17.07.2020 12:25, Richard Sandiford wrote:
Dmitrij Pochepko writes:
Hi,
please take a look at updated patch with all comments addressed (attached).
Thanks, pushed to master with a slightly tweaked changelog.
Richard
Thank you!
On 17.07.2020 12:21, Richard Sandiford wrote:
Dmitrij Pochepko writes:
Hi,
I please take a look at new version (attached).
Thanks, pushed to master with a slightly tweaked changelog.
Richard
On 17/11/19 22:31 +0100, François Dumont wrote:
This is an implementation of PR 68303.
I try to use this idea as much as possible to avoid computation of
hash codes.
Note that tests are not showing any gain. I guess hash computation
must be quite bad to get a benefit from it. So I am only a
On 7/17/20 3:37 AM, Richard Biener wrote:
On Thu, Jul 16, 2020 at 7:39 PM Nathan Sidwell wrote:
On 7/16/20 11:56 AM, Iain Sandoe wrote:
Hello folks,
It's unfortunate the original plan of handling lifetime issues in a
gimple pass didn't work out.
OK for master?
OK for 10.x?
IMHO too big
On Fri, Jul 17, 2020 at 12:08 AM Richard Biener wrote:
>
> On Wed, 15 Jul 2020, Joseph Myers wrote:
>
> > On Wed, 15 Jul 2020, Richard Biener wrote:
> >
> > > But note one of the issues is that when not cross-compiling we're
> > > using a single libiberty for target and host objects (likewise
> >
On Fri, Jul 17, 2020 at 12:03 AM Richard Biener wrote:
>
> On Wed, 15 Jul 2020, H.J. Lu wrote:
>
> > On Wed, Jul 15, 2020 at 8:20 AM Richard Biener wrote:
> > >
> > > On Wed, 15 Jul 2020, H.J. Lu wrote:
> > >
> > > > With --enable-cet, require CET support only for the final GCC build.
> > > > Don
Yes that is correct. GCC simply checks if a symbol is part of a comdat
group and if it is, emits .linkonce for it's section. GAS then sees
the directive and moves the symbol corresponding to the section name
to be the first symbol so it becomes the key. See:
https://github.com/bminor/binutils-gdb/b
On Thu, Jul 16, 2020 at 7:50 PM H.J. Lu wrote:
>
> On Mon, Jul 13, 2020 at 9:12 AM H.J. Lu wrote:
> >
> > On Thu, Jul 9, 2020 at 6:35 AM H.J. Lu wrote:
> > >
> > > On Thu, Jul 9, 2020 at 5:04 AM Kirill Yukhin
> > > wrote:
> > > >
> > > > On 07 июл 09:06, H.J. Lu wrote:
> > > > > On Tue, Jul 7,
> The COFF linker errors with a multiple reference error before the
> lto-wrapper process is started. If I understand correctly this is due
> to how COMDAT works in PE/COFF as the associated string to the COMDAT
> section is stored in the symbol table. When using the
> --allow-multiple-definition f
On 17/07/2020 12:29, Andrew Stubbs wrote:
For easier later maintenance, shouldn't this be a '#define' (or similar)
done next to where the GCC back end defines its default?
I thought of this, but I don't think there's actually a problem. The
default is defined via OPTION_DEFAULT_SPECS, so there
The COFF linker errors with a multiple reference error before the
lto-wrapper process is started. If I understand correctly this is due
to how COMDAT works in PE/COFF as the associated string to the COMDAT
section is stored in the symbol table. When using the
--allow-multiple-definition flag as a w
On 19/12/19 20:22 +0100, François Dumont wrote:
Because of this change printers.py has to be updated too.
François
On 11/17/19 10:15 PM, François Dumont wrote:
H1 used to be a reference to the user Hash, now _Hashtable and
unordered types agree on the same Hash type which is more intuitive
On 17/07/2020 07:20, Thomas Schwinge wrote:
--- a/gcc/config/gcn/mkoffload.c
+++ b/gcc/config/gcn/mkoffload.c
@@ -33,31 +33,53 @@
#include
#include "collect-utils.h"
#include "gomp-constants.h"
+#include "simple-object.h"
+#include "elf.h"
+
+/* These probably won't be in elf.h for a while
Hi Julian, Tobias!
On 2020-07-15T12:28:42+0200, Thomas Schwinge wrote:
> On 2020-07-14T13:43:37+0200, I wrote:
>> On 2020-06-16T15:39:44-0700, Julian Brown wrote:
>>> As mentioned in the blurb for the previous patch, an "attach" operation
>>> for a Fortran pointer with an array descriptor must c
On 19/11/19 00:10 +0200, Ville Voutilainen wrote:
On Mon, 18 Nov 2019 at 23:41, François Dumont wrote:
> Also, is
> this ABI-compatible
> for our unordered containers?
>
IMHO, yes it is.
In hashtable_policy.h _H1 was the user hash which I renamed in _Hash,
the same template name that for un
On 17/11/19 22:03 +0100, François Dumont wrote:
Simplify local_iterator implementation. It makes local_iterator and
iterator comparable which is used in debug containers.
   * include/bits/hashtable_policy.h (_Node_iterator_base()): New.
   (operator==(const _Node_iterator_base&, const
On 16/12/19 08:18 +0100, François Dumont wrote:
A small refresh on this patch now tested also for versioned namespace
which require printers.py to be updated.
Note that this simplification works also for normal mode so I can
apply it independently from the stl_bvector.h part.
   * incl
N.B. the 0/6 entry of a patch series is supposed to be a cover letter
describing the changes in the series, not one of the patches.
If you have patches 0/6, 1/6, 2/6 ... 6/6 then you actually have seven
patches, not six!
Anyway ...
On 19/12/19 20:17 +0100, François Dumont wrote:
diff --git a/
On 17/11/19 21:59 +0100, François Dumont wrote:
This patch adds noexcept qualification on allocator aware constructors
and fix the one on the default constructor.
   * include/bits/hashtable.h
   (_Hashtable(_Hashtable&& __ht, __node_alloc_type&& __a, true_type)):
   Add noexcept q
Hi,
Sorry for the slow review.
> The new version v7 is attached which has addressed your review comments
> on v6. Could you have a further look? Many thanks in advance!
>
> Bootstrapped/regtested on aarch64-linux-gnu and powerpc64le-linux-gnu P9.
> Even with explicit vect-partial-vector-usage s
On 17/11/19 21:56 +0100, François Dumont wrote:
This patch avoids over-sizing of the container by rather considering
the bucket count hint or potential reservation.
It concerns only the non-multi containers.
   * include/bits/hashtable.h
   (_Hashtable<>(_InputIterator, _InputIterator
On 17/11/19 21:51 +0100, François Dumont wrote:
This patch simplifies a number of implementations.
It tries as much as possible to avoid computing hash code. This is
especially true for the erase implementation in case of multi keys.
   * include/bits/hashtable_policy.h (_Map_base<>::at
On 17/07/20 09:39 +0100, Mike Crowe via Libstdc++ wrote:
On Friday 29 May 2020 at 07:17:26 +0100, Mike Crowe wrote:
This series ensures that the std::future::wait_* functions use
std::chrono::steady_clock when required, introduces
std::chrono::__detail::ceil to make that easier to do, and then m
Dmitrij Pochepko writes:
> Hi,
>
> please take a look at updated patch with all comments addressed (attached).
Thanks, pushed to master with a slightly tweaked changelog.
Richard
On 17/07/20 10:05 +0100, Iain Sandoe wrote:
Hi
As per http://eel.is/c++draft/coroutine.trivial.awaitables the methods for
the trivial awaitables are supposed to be constexpr.
tested on x86_64-linux, darwin powerpc64-linux,
OK for master?
for 10.3?
OK for both, thanks.
Dmitrij Pochepko writes:
> Hi,
>
> I please take a look at new version (attached).
Thanks, pushed to master with a slightly tweaked changelog.
Richard
Tamar Christina writes:
> Hi Richard,
>
> I have fixed the formatting issues and made it so it checks explicitly
> for ':'.
>
> Ok for master, GCC 10, 9 and 8 after some stew?
OK, thanks. Some trivial formatting bits below (sorry)…
> diff --git a/gcc/config/aarch64/driver-aarch64.c
> b/gcc/con
Hi Julian!
On 2020-07-16T22:21:43+0100, Julian Brown wrote:
> On Thu, 16 Jul 2020 11:35:23 +0200
> Thomas Schwinge wrote:
>> On 2020-06-26T11:20:40+0200, I wrote:
>> > On 2019-12-17T22:03:47-0800, Julian Brown
>> > wrote:
>> >> This part contains the libgomp runtime support for the
>> >> GOMP_M
Hi
As per http://eel.is/c++draft/coroutine.trivial.awaitables the methods for
the trivial awaitables are supposed to be constexpr.
tested on x86_64-linux, darwin powerpc64-linux,
OK for master?
for 10.3?
thanks
Iain
---
The methods of the trivial awaitables are intended to
be constexpr.
xiezhiheng writes:
>> -Original Message-
>> From: Richard Sandiford [mailto:richard.sandif...@arm.com]
>> Sent: Thursday, July 16, 2020 8:42 PM
>> To: xiezhiheng
>> Cc: Richard Biener ; gcc-patches@gcc.gnu.org
>> Subject: Re: [PATCH PR94442] [AArch64] Redundant ldp/stp instructions
>> emi
contrib/ChangeLog:
* gcc-changelog/git_update_version.py: Fix typo.
Committed as obvious.
commit 0c1d1c01039a96c191a7aded40e5df40b14d387a
Author: Jonathan Wakely
Date: Fri Jul 17 09:53:19 2020
gcc-changelog: Fix typo in output
contrib/ChangeLog:
* gcc-ch
On Friday 29 May 2020 at 07:17:26 +0100, Mike Crowe wrote:
> This series ensures that the std::future::wait_* functions use
> std::chrono::steady_clock when required, introduces
> std::chrono::__detail::ceil to make that easier to do, and then makes
> use of that function to simplify and improve th
In s390_expand_insv the movstrict patterns are always generated with a
CC clobber although only movstricthi actually needs one. The patch
invokes the expanders instead of constructing the pattern by hand.
Bootstrapped and regression tested on s390x.
Committed to mainline
gcc/ChangeLog:
On Fri, Jul 17, 2020 at 7:15 AM Sunil Pandey wrote:
>
> Any comment on revised patch? At least, in finish_decl, decl global
> attributes are populated.
+static void
+ix86_lower_local_decl_alignment (tree decl)
+{
+ unsigned new_align = LOCAL_DECL_ALIGNMENT (decl);
please use the macro-expande
> Oh! Sent out v3 with tweaked description as
> https://gcc.gnu.org/pipermail/gcc-patches/2020-July/550168.html
Thanks.
> I don't have a push access to gcc tree. Should I request one via
> https://sourceware.org/cgi-bin/pdw/ps_form.cgi ?
Sure, you can put me (ebotca...@libertysurf.fr) as
On Thu, Jul 16, 2020 at 7:39 PM Nathan Sidwell wrote:
>
> On 7/16/20 11:56 AM, Iain Sandoe wrote:
> > Hello folks,
>
> It's unfortunate the original plan of handling lifetime issues in a
> gimple pass didn't work out.
>
> > OK for master?
> >
> > OK for 10.x?
IMHO too big of a change for 10.2 but
On Thu, Jul 16, 2020 at 3:05 PM Markus Böck via Gcc-patches
wrote:
>
> COFF targets currently do not support COMDAT groups. On MinGW targets
> GCC instead puts symbols part of a COMDAT group inside of sections
> annotated with the .linkonce GAS directive. This leads to GAS
> generating a section s
On Thu, Jul 16, 2020 at 1:07 PM Roger Sayle wrote:
>
>
> Hi Richard,
>
> Many thanks. As promised, here's a clean-up patch that removes the last
> direct
> call to targetm.truly_noop_truncation from the middle-end, allowing this hook
> at some point in the future to take modes instead of sizes.
ping!
On Fri, Jul 10, 2020 at 5:24 PM Hongtao Liu wrote:
>
> + maintainer.
> cc H.J
>
> On Thu, Jul 9, 2020 at 4:33 PM Hongtao Liu wrote:
> >
> > Hi:
> > For a constant vector having one duplicated value, there's no need
> > to put the whole vector in the constant pool, using embedded broadcas
On Wed, 15 Jul 2020, Joseph Myers wrote:
> On Wed, 15 Jul 2020, Richard Biener wrote:
>
> > But note one of the issues is that when not cross-compiling we're
> > using a single libiberty for target and host objects (likewise
>
> There shouldn't be a target libiberty, since commit
> 8499116aa30a
On Wed, 15 Jul 2020, H.J. Lu wrote:
> On Wed, Jul 15, 2020 at 8:20 AM Richard Biener wrote:
> >
> > On Wed, 15 Jul 2020, H.J. Lu wrote:
> >
> > > With --enable-cet, require CET support only for the final GCC build.
> > > Don't enable CET without CET support in stage1 nor for build support.
> >
>
59 matches
Mail list logo
