On 24.05.2018 21:59, Jakub Jelinek wrote:
> On Thu, May 24, 2018 at 12:56:23PM -0700, H.J. Lu wrote:
This patch uses pre-computed size of struct ustat for Linux.
PR sanitizer/85835
* sanitizer_common/sanitizer_platform_limits_posix.cc: Don't
include for L
On 09/20/2018 10:01 PM, Thomas Koenig wrote:
Hi Damian,
On a related note, two Sourcery Institute developers have attempted to
edit
the GCC build system to make the downloading and building of OpenCoarrays
automatically part of the gfortran build process. Neither developer
succeeded.
We ad
On Thu, Sep 20, 2018 at 11:56:37PM -0400, Marek Polacek wrote:
> The patch for P0595R1 - is_constant_evaluated had this hunk:
>
> @@ -5279,7 +5315,9 @@ maybe_constant_init_1 (tree t, tree decl, bool
> allow_non_constant)
>else if (CONSTANT_CLASS_P (t) && allow_non_constant)
> /* No evalu
On Wed, 23 Apr 2014 at 10:58, Konstantin Serebryany
wrote:
>
> Thanks. Let's move the discussion there.
4-early ping..
Thanks to Yuri for his remark there.
Just asking if any of you folks had more comments?
thanks,
>
> On Wed, Apr 23, 2014 at 12:46 PM, Bernhard Reutner-Fischer
> wrote:
> > On 1
On 9/21/18 6:05 AM, Bin.Cheng wrote:
> On Thu, Sep 20, 2018 at 6:43 PM Jan Hubicka wrote:
>>
>>> On Thu, Sep 20, 2018 at 5:26 PM Jan Hubicka wrote:
> On Thu, Sep 20, 2018 at 2:11 AM Martin Liška wrote:
>>
>> Hello.
>>
>> I've been working for some time on a patch that si
PING
On Wed, Sep 12, 2018 at 10:17 PM Janne Blomqvist
wrote:
> When producing error and warning messages, libgfortran writes a
> message by using many system calls. By using vectored writes (the
> POSIX writev function) when available and feasible to use without
> major surgery, we reduce the c
PING^1
On 9/12/18 2:39 PM, Martin Liška wrote:
> Hi.
>
> This is follow-up of:
> https://gcc.gnu.org/ml/gcc/2018-08/msg7.html
>
> I've chosen to implement that with new DECL_CXX_LAMBDA_FUNCTION that
> uses an empty bit in tree_function_decl.
>
> Patch can bootstrap on ppc64le-redhat-linux a
PING^1
On 9/12/18 2:37 PM, Martin Liška wrote:
> Hi.
>
> The patch improves locations of the warning in following way:
>
> sample.c: In function ‘main’:
> sample.c:16:1: error: source locations for function ‘main’ have changed, the
> profile data may be out of date [-Werror=coverage-mismatch]
>
Hi.
This is removal of some Pascal-related comments.
Patch survives regression tests on x86_64-linux-gnu.
Ready for trunk?
Martin
gcc/ChangeLog:
2018-09-19 Martin Liska
* config/powerpcspe/powerpcspe.c (rs6000_output_function_epilogue):
Do not handle "GNU Pascal".
*
Hi.
Following patch marks releases memory blocks as not accesible for valgrind.
That can help us in the future in order to catch memory corruptions.
Ready for trunk?
Martin
gcc/ChangeLog:
2018-09-21 Martin Liska
* memory-block.h (memory_block_pool::release): Annotate with
va
The packed record layout is not really supported for the time being.
Tested on x86-64/Linux, applied on the mainline.
2018-09-21 Eric Botcazou
* c-ada-spec.c: Include diagnostic.h.
(dump_ada_declaration) : Issue a warning on packed layout.
2018-09-21 Eric Botcazou
On 21/09/18 01:52, Hans-Peter Nilsson wrote:
>> Date: Thu, 20 Sep 2018 15:22:23 +0100
>> From: Jonathan Wakely
>
>> On 20/09/18 15:36 +0200, Christophe Lyon wrote:
>>> On Wed, 19 Sep 2018 at 23:13, Rainer Orth
>>> wrote:
Hi Christophe,
> I have noticed failures on hypot-long-
On 21/09/18 02:52 +0200, Hans-Peter Nilsson wrote:
Date: Thu, 20 Sep 2018 15:22:23 +0100
From: Jonathan Wakely
On 20/09/18 15:36 +0200, Christophe Lyon wrote:
>On Wed, 19 Sep 2018 at 23:13, Rainer Orth
wrote:
>>
>> Hi Christophe,
>>
>> > I have noticed failures on hypot-long-double.cc on ar
On 21/09/18 11:24 +0100, Richard Earnshaw (lists) wrote:
On 21/09/18 01:52, Hans-Peter Nilsson wrote:
Date: Thu, 20 Sep 2018 15:22:23 +0100
From: Jonathan Wakely
On 20/09/18 15:36 +0200, Christophe Lyon wrote:
On Wed, 19 Sep 2018 at 23:13, Rainer Orth wrote:
Hi Christophe,
I have notic
On 21/09/18 11:34, Jonathan Wakely wrote:
> On 21/09/18 11:24 +0100, Richard Earnshaw (lists) wrote:
>> On 21/09/18 01:52, Hans-Peter Nilsson wrote:
Date: Thu, 20 Sep 2018 15:22:23 +0100
From: Jonathan Wakely
>>>
On 20/09/18 15:36 +0200, Christophe Lyon wrote:
> On Wed, 19 Sep 2
Ilya Leoshkevich wrote:
> 2018-09-19 Ilya Leoshkevich
>
> PR target/80080
> * config/s390/s390.md: Do not use PARALLEL RETURN+USE when
> returning via %r14.
This makes sense to me. I'm just wondering if it wouldn't be
simpler to do the check for r14 right in s390_emit_epilo
2018-09-21 Florian Weimer
PR middle-end/81035
* doc/extend.texi (Common Function Attributes): Mention that
noreturn suppresses tail call optimization.
diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index e3312aa8b42..909e7a17357 100644
--- a/gcc/doc/extend.texi
> Am 21.09.2018 um 12:50 schrieb Ulrich Weigand :
>
> Ilya Leoshkevich wrote:
>
>> 2018-09-19 Ilya Leoshkevich
>>
>> PR target/80080
>> * config/s390/s390.md: Do not use PARALLEL RETURN+USE when
>> returning via %r14.
>
> This makes sense to me. I'm just wondering if it would
On 21/09/18 11:39 +0100, Richard Earnshaw (lists) wrote:
On 21/09/18 11:34, Jonathan Wakely wrote:
On 21/09/18 11:24 +0100, Richard Earnshaw (lists) wrote:
On 21/09/18 01:52, Hans-Peter Nilsson wrote:
Date: Thu, 20 Sep 2018 15:22:23 +0100
From: Jonathan Wakely
On 20/09/18 15:36 +0200, Chri
Hi Jakub,
are your concerns addressed with this answer, or do you have objections
to this patch?
Thanks
Bernd.
On 09/14/18 21:06, Bernd Edlinger wrote:
> On 09/14/18 21:01, Jakub Jelinek wrote:
>> On Fri, Sep 14, 2018 at 06:39:38PM +, Bernd Edlinger wrote:
>>> Hi,
>>>
>>> this is an upate
On Fri, Sep 21, 2018 at 11:36:53AM +, Bernd Edlinger wrote:
> are your concerns addressed with this answer, or do you have objections
> to this patch?
No objections, but no time to review your patch either right now.
Jakub
Hello,
The inclusion of vxworks-dummy.h in tm_file by config.gcc
is spread in various places without a clear rationale.
The attached patch just factorizes this out, at the end
of the tm_file construction steps to account for sections
totally redefining the variable contents, and with a head
comme
Hi Shaokun,
On 20/09/18 15:54, Zhangshaokun wrote:
Hi James,
On 2018/9/20 22:22, James Greenhalgh wrote:
On Wed, Sep 19, 2018 at 04:53:52AM -0500, Shaokun Zhang wrote:
This patch adds HiSilicon's an mcpu: tsv110, which supports v8_4A.
It has been tested on aarch64 and no regressions from this
> Date: Fri, 21 Sep 2018 12:21:31 +0100
> From: Jonathan Wakely
> Here's the corrected patch, any objections to this?
Quite the contrary; LGTM.
brgds, H-P
On Fri, Sep 21, 2018 at 12:50:40PM +0200, Ulrich Weigand wrote:
> Ilya Leoshkevich wrote:
>
> > 2018-09-19 Ilya Leoshkevich
> >
> > PR target/80080
> > * config/s390/s390.md: Do not use PARALLEL RETURN+USE when
> > returning via %r14.
>
> This makes sense to me. I'm just wonderin
On Wed, 2018-09-19 at 15:51 +0200, Richard Biener wrote:
> On Wed, Sep 19, 2018 at 12:42 PM David Malcolm
> wrote:
> >
> > In r262891 I reimplemented this call:
> > dump_printf_loc (MSG_NOTE, loc, "=== %s ===\n", name);
> > in dump_begin_scope to use direct calls to dump_loc:
> > if (dump_fil
Hi Will,
On Thu, Sep 20, 2018 at 01:52:55PM -0500, Will Schmidt wrote:
> This updates those powerpc testsuite tests that are using the
> vec_splat() builtin with an invalid arg1. Per discussions during the
> review of gimple-folding for vec_splat(), it was clarified
> that arg1 for vec_splat()
On 09/20/2018 03:06 AM, Richard Biener wrote:
On Wed, Sep 19, 2018 at 4:19 PM Martin Sebor wrote:
On 09/18/2018 10:23 PM, Jeff Law wrote:
On 9/18/18 1:46 PM, Martin Sebor wrote:
On 09/18/2018 12:58 PM, Jeff Law wrote:
On 9/18/18 11:12 AM, Martin Sebor wrote:
My bad. Sigh. CCP doesn't tra
On Tue, Sep 18, 2018 at 03:34:25PM -0500, Will Schmidt wrote:
> The expected codegen for this testcase with target {le} and
> option -mcpu=power8 is lxvd2x and stxvd2x. It was initially
> committed with contents as seen on builds for P7, which was
> incorrect. Update as is appropriate.
> 2018-09
On Fri, Sep 21, 2018 at 09:37:53AM +0200, Jakub Jelinek wrote:
> On Thu, Sep 20, 2018 at 11:56:37PM -0400, Marek Polacek wrote:
> > The patch for P0595R1 - is_constant_evaluated had this hunk:
> >
> > @@ -5279,7 +5315,9 @@ maybe_constant_init_1 (tree t, tree decl, bool
> > allow_non_constant)
> >
Hi, this is the 4th version of the patch.
mainly address Martin’s comments on some spelling issues.
I have tested the patch on both x86 and aarch64, no issue.
Okay for commit?
thanks.
Qing.
gcc/ChangeLog
+2018-09-20 Qing Zhao
+
+ * cif-code.def (FUNCTION_EXTERN): New CIFCODE.
+
On Fri, Sep 21, 2018 at 11:04 AM, Marek Polacek wrote:
> On Fri, Sep 21, 2018 at 09:37:53AM +0200, Jakub Jelinek wrote:
>> On Thu, Sep 20, 2018 at 11:56:37PM -0400, Marek Polacek wrote:
>> > The patch for P0595R1 - is_constant_evaluated had this hunk:
>> >
>> > @@ -5279,7 +5315,9 @@ maybe_constant
On Fri, 31 Aug 2018 at 16:09, Christophe Lyon
wrote:
>
> On Wed, 29 Aug 2018 at 12:46, Kyrill Tkachov
> wrote:
> >
> > Hi Christophe,
> >
> > On 13/07/18 17:10, christophe.l...@st.com wrote:
> > > From: Christophe Lyon
> > >
> > > 2018-XX-XX Christophe Lyon
> > > Mickaël Guêné
> > >
On 21/09/18 15:48 +0200, Hans-Peter Nilsson wrote:
Date: Fri, 21 Sep 2018 12:21:31 +0100
From: Jonathan Wakely
Here's the corrected patch, any objections to this?
Quite the contrary; LGTM.
Committed to trunk.
Here is the patch complement.
load_factor.cc failure revealed a bug in load factor management. Now
computation of _M_next_resize is consistent throughout the different
places where it is set.
The 2 other tests only have to be adapted.
PR libstdc++/87135
* src/c++11/hashtable_c++0x.cc
Hi Carl,
Sorry for the late review.
On Mon, Sep 17, 2018 at 03:03:28PM -0700, Carl Love wrote:
> * config/rs6000.c (rs6000_expand_mtfsb0_mtfsb1_builtin): Add.
config/rs6000/rs6000.c
> +RS6000_BUILTIN_X (RS6000_BUILTIN_MTFSB0, "__builtin_mtfsb0",
> + RS6000_BTM_ALWAYS,
> +
My apologies for kidnapping this thread:
On 9/20/18 1:01 PM, Thomas Koenig wrote:
Hi Damian,
On a related note, two Sourcery Institute developers have attempted to
edit
the GCC build system to make the downloading and building of OpenCoarrays
automatically part of the gfortran build process.
Janne, this looks OK. Since you are touching on configuration and posix
dependencies have you tested under any other systems?
Jerry
On 9/21/18 1:41 AM, Janne Blomqvist wrote:
PING
On Wed, Sep 12, 2018 at 10:17 PM Janne Blomqvist
wrote:
When producing error and warning messages, libgfortran
On Fri, 21 Sep 2018, Martin Liška wrote:
> Hi.
>
> This is removal of some Pascal-related comments.
There are two different kinds of comments being removed here. There are
comments relating to GNU Pascal, which has long been a dead project, so
removing those seems reasonable. But there are a
On 21/09/18 18:10 +0200, François Dumont wrote:
Here is the patch complement.
load_factor.cc failure revealed a bug in load factor management. Now
computation of _M_next_resize is consistent throughout the different
places where it is set.
The 2 other tests only have to be adapted.
PR l
On 09/17/2018 07:30 PM, Jeff Law wrote:
On 8/28/18 6:12 PM, Martin Sebor wrote:
Sadly, dstbase is the PARM_DECL for d. That's where things are going
"wrong". Not sure why you're getting the PARM_DECL in that case. I'd
debug get_addr_base_and_unit_offset to understand what's going on.
Essentia
This bug was something of a disaster for Jeurgen Reuter and so I set
to it right away. Jeurgen's reduction of the failing programs save a
huge amount of time and the fix turned out to be a one-liner.
Committed after testing by Dominique.
Bootstrapped and regtested on FC28/x86_64.
Paul
Author: p
On Fri, Sep 21, 2018 at 11:19:34AM -0400, Jason Merrill wrote:
> On Fri, Sep 21, 2018 at 11:04 AM, Marek Polacek wrote:
> > On Fri, Sep 21, 2018 at 09:37:53AM +0200, Jakub Jelinek wrote:
> >> On Thu, Sep 20, 2018 at 11:56:37PM -0400, Marek Polacek wrote:
> >> > The patch for P0595R1 - is_constant_
This is yet another deferred character problem occurring at exactly
the same place as 87239 and 84109. I found another bug while going
along and so have fixed that too.
Bootstrapped and regtested on FC28/x86_64.
I will apply all three to 8-branch in slightly more than one week's time.
Paul
2018
On Fri, Sep 21, 2018 at 12:59:27PM +0200, Florian Weimer wrote:
> 2018-09-21 Florian Weimer
>
> PR middle-end/81035
> * doc/extend.texi (Common Function Attributes): Mention that
> noreturn suppresses tail call optimization.
> +In order to preserve backtraces, GCC will never
On Fri, Sep 21, 2018 at 7:37 PM Jerry DeLisle wrote:
> Janne, this looks OK.
Thanks, committed as r264487.
Since you are touching on configuration and posix
> dependencies have you tested under any other systems?
>
No, unfortunately I don't have easy access to such a system for testing.
The p
* Segher Boessenkool:
> On Fri, Sep 21, 2018 at 12:59:27PM +0200, Florian Weimer wrote:
>> 2018-09-21 Florian Weimer
>>
>> PR middle-end/81035
>> * doc/extend.texi (Common Function Attributes): Mention that
>> noreturn suppresses tail call optimization.
>
>> +In order to preserv
> On Sep 21, 2018, at 2:17 PM, Florian Weimer wrote:
>
> * Segher Boessenkool:
>
>> On Fri, Sep 21, 2018 at 12:59:27PM +0200, Florian Weimer wrote:
>>> 2018-09-21 Florian Weimer
>>>
>>> PR middle-end/81035
>>> * doc/extend.texi (Common Function Attributes): Mention that
>>> no
* Paul Koning:
>> On Sep 21, 2018, at 2:17 PM, Florian Weimer wrote:
>>
>> * Segher Boessenkool:
>>
>>> On Fri, Sep 21, 2018 at 12:59:27PM +0200, Florian Weimer wrote:
2018-09-21 Florian Weimer
PR middle-end/81035
* doc/extend.texi (Common Function Attributes): Men
Yes.
On Fri, Sep 21, 2018 at 1:40 PM, Marek Polacek wrote:
> On Fri, Sep 21, 2018 at 11:19:34AM -0400, Jason Merrill wrote:
>> On Fri, Sep 21, 2018 at 11:04 AM, Marek Polacek wrote:
>> > On Fri, Sep 21, 2018 at 09:37:53AM +0200, Jakub Jelinek wrote:
>> >> On Thu, Sep 20, 2018 at 11:56:37PM -0400
On Fri, Sep 21, 2018 at 7:25 PM Jerry DeLisle wrote:
> My apologies for kidnapping this thread:
> On 9/20/18 1:01 PM, Thomas Koenig wrote:
> > Hi Damian,
> >
> >> On a related note, two Sourcery Institute developers have attempted to
> >> edit
> >> the GCC build system to make the downloading and
On September 21, 2018 6:24:45 PM GMT+02:00, Jerry DeLisle
wrote:
>My apologies for kidnapping this thread:
>On 9/20/18 1:01 PM, Thomas Koenig wrote:
>> Hi Damian,
>>
>>> On a related note, two Sourcery Institute developers have attempted
>to
>>> edit
>>> the GCC build system to make the downloa
On 9/21/18 4:59 AM, Florian Weimer wrote:
> 2018-09-21 Florian Weimer
>
> PR middle-end/81035
> * doc/extend.texi (Common Function Attributes): Mention that
> noreturn suppresses tail call optimization.
OK.
jeff
On 9/21/18 3:24 AM, Martin Liška wrote:
> Hi.
>
> Following patch marks releases memory blocks as not accesible for valgrind.
> That can help us in the future in order to catch memory corruptions.
>
> Ready for trunk?
> Martin
>
> gcc/ChangeLog:
>
> 2018-09-21 Martin Liska
>
> * memor
On 9/12/18 6:37 AM, Martin Liška wrote:
> Hi.
>
> The patch improves locations of the warning in following way:
>
> sample.c: In function ‘main’:
> sample.c:16:1: error: source locations for function ‘main’ have changed, the
> profile data may be out of date [-Werror=coverage-mismatch]
> 16 | }
Use the proper type for "complain".
I guess it's obvious, but anyway, bootstrapped/regtested on x86_64-linux, ok
for trunk?
2018-09-21 Marek Polacek
* cp-tree.h (build_noexcept_spec, add_exception_specifier): Adjust
declarations.
* except.c (build_noexcept_spec): Chang
Ok.
On Sep 19, 2018, at 1:36 PM, Iain Buclaw wrote:
>
> On 18 September 2018 at 02:36, Iain Buclaw wrote:
>>
>> This patch adds D language support to the GCC testsuite.
>>
>> As well as generating the DejaGNU options for compile and link tests,
>> handles the conversion from DMD-style compiler opt
On 21 September 2018 at 22:04, Mike Stump wrote:
> On Sep 19, 2018, at 1:36 PM, Iain Buclaw wrote:
>>
>> On 18 September 2018 at 02:36, Iain Buclaw wrote:
>>>
>>> This patch adds D language support to the GCC testsuite.
>>>
>>> As well as generating the DejaGNU options for compile and link tests
On Fri, Sep 21, 2018 at 9:25 AM Jerry DeLisle wrote:
> The actual library source code is contained mostly in one source file.
There are as many files as there are options for the underlying
parallel programming
model. The default is MPI, but I've co-authored conference papers last year
and this
On Sep 19, 2018, at 1:49 PM, Iain Buclaw wrote:
>
> On 18 September 2018 at 02:38, Iain Buclaw wrote:
>> This patch add the Phobos runtime library and license (Boost) files.
>> Phobos is the standard runtime library that comes with the D language
>> compiler. The bulk of which is comprised most
On Sep 17, 2018, at 5:37 PM, Iain Buclaw wrote:
>
> This patch adds a further number of tests, but were added as part of
> fixing gdc-specific bugs.
Ok. Trivial, and self-review applicable.
On Sep 17, 2018, at 5:36 PM, Iain Buclaw wrote:
>
> This patch adds part of the D2 testsuite, which includes D source code
> files that are considered compilable; files that are considered
> uncompilable, but should not ICE; and files that should execute on
> targets with crash or assertion failu
On Sep 17, 2018, at 5:37 PM, Iain Buclaw wrote:
> This patch adds a further number of tests, but were added as part of
> fixing gdc-specific bugs.
Ok. Trivial, and self-review applicable.
This is v2 of the patch; I managed to bit-rot my own patch due to my
fix for r264335, which tightened up the "is this meaningful" threshold
on edit distances when finding spelling correction candidates.
The only change in this version is to rename various things in
the testcase so that they contin
On 21 September 2018 at 22:54, Mike Stump wrote:
> On Sep 17, 2018, at 5:36 PM, Iain Buclaw wrote:
>>
>> This patch adds part of the D2 testsuite, which includes D source code
>> files that are considered compilable; files that are considered
>> uncompilable, but should not ICE; and files that sh
On Fri, Sep 21, 2018 at 08:36:45PM +0200, Florian Weimer wrote:
> * Paul Koning:
>
> >> On Sep 21, 2018, at 2:17 PM, Florian Weimer wrote:
> >>
> >> * Segher Boessenkool:
> >>
> >>> On Fri, Sep 21, 2018 at 12:59:27PM +0200, Florian Weimer wrote:
> 2018-09-21 Florian Weimer
>
> >>>
On Fri, 21 Sep 2018 03:14:22 +0200
Bernhard Reutner-Fischer wrote:
> > diff --git a/gcc/fortran/trans-array.c b/gcc/fortran/trans-array.c
> > index 95ea615..2ac5908 100644
> > --- a/gcc/fortran/trans-array.c
> > +++ b/gcc/fortran/trans-array.c
> > @@ -88,6 +88,7 @@ along with GCC; see the file CO
Attached is the refreshed patch for trunk.
After commit 264462 (Remove arc profile histogram in non-LTO mode.), the API
of get_coverage_counts was changed a bit. So the main difference between the
current version of my patch from the previous one is that :
Now I use
+ if (counter == GCOV_CO
On 9/21/18 1:16 PM, Damian Rouson wrote:> On Fri, Sep 21, 2018 at 9:25
AM Jerry DeLisle wrote:
>
>> The actual library source code is contained mostly in one source file.
>
> There are as many files as there are options for the underlying
> parallel programming
> model. The default is MPI, but
Hi Kyrill,
On 2018/9/21 20:25, Kyrill Tkachov wrote:
> Hi Shaokun,
>
> On 20/09/18 15:54, Zhangshaokun wrote:
>> Hi James,
>>
>> On 2018/9/20 22:22, James Greenhalgh wrote:
>>> On Wed, Sep 19, 2018 at 04:53:52AM -0500, Shaokun Zhang wrote:
This patch adds HiSilicon's an mcpu: tsv110, which s
71 matches
Mail list logo
