On 10/12/2016 01:04 PM, Markus Trippelsdorf wrote:
I'm more concerned about the first impression that people will get from
this warning. If the fist couple of samples they will look at are
clearly bogus (as with the example comments above) they will very
quickly disable the warning.
And if a sma
* Claudiu Zissulescu [2016-06-30 12:24:12
+0200]:
> The mululw instructions are wrongly used in the patterns, fix them.
>
> Okt to apply?
> Claudiu
>
> gcc/
> 2016-06-28 Claudiu Zissulescu
>
> * config/arc/arc.md (umul_600): Change.
> (umul64_600): Likewise.
Looks fine, though
On Tue, Oct 11, 2016 at 03:29:54PM -0600, Martin Sebor wrote:
> >+signed int vec_cntlz_lsbb (vector signed char);
> >+signed int vec_cntlz_lsbb (vector unsigned char)
> >+
> >+signed int vec_cnttz_lsbb (vector signed char);
> >+signed int vec_cnttz_lsbb (vector unsigned char);
> ...
> >+The @code{v
On 10/07/2016 01:13 PM, Jakub Jelinek wrote:
> Hi!
>
Hi Jakub.
Again thanks for detailed review, you found many improvements.
> Ok, first let me list some needed follow-ups that don't need to be handled
> right away:
> - r237814-like changes for ASAN_MARK
Yes, that's missing. I'm wondering whe
On 10/12/2016 03:01 PM, Bernd Schmidt wrote:
> On 10/10/2016 09:32 PM, Pedro Alves wrote:
>> From: Pedro Alves
>> Date: 2016-10-10 19:25:47 +0100
>>
>> Move OVERRIDE/FINAL from gcc/coretypes.h to include/ansidecl.h
>>
>> So that GDB and other projects that share the top level can use them.
>
> Se
On 10/12/2016 04:09 PM, Pedro Alves wrote:
Thanks. Here's a follow up patch that I was just testing.
Need this if building with "g++ -std=gnu++11", with gcc < 4.7.
Lovely. That's ok too if the other one goes in.
Bernd
On Wed, Oct 12, 2016 at 04:04:25PM +0200, Bernd Schmidt wrote:
> On 10/12/2016 01:04 PM, Markus Trippelsdorf wrote:
> >I'm more concerned about the first impression that people will get from
> >this warning. If the fist couple of samples they will look at are
> >clearly bogus (as with the example c
On 2016-10-12 9:48 AM, Jason Merrill wrote:
On Wed, Oct 12, 2016 at 4:02 AM, Jakub Jelinek wrote:
On Wed, Oct 12, 2016 at 09:52:04AM +0200, Florian Weimer wrote:
dropping the alignment means that the padding before the lock member
vanishes. Consequently, we have just created a silent ABI chan
On Sat, Oct 8, 2016 at 1:07 PM, Prathamesh Kulkarni
wrote:
> On 7 October 2016 at 17:49, David Malcolm wrote:
>> On Fri, 2016-10-07 at 10:33 +0530, Prathamesh Kulkarni wrote:
>>> On 22 September 2016 at 23:15, Joseph Myers
>>> wrote:
>>> > On Thu, 22 Sep 2016, Prathamesh Kulkarni wrote:
>>> >
>>
This patch to libgo by James Clarke fixes libgo for sparc64. The
getrandom syscall was being ignored because the file was named
"sparc". The clone syscall apparently needs special attention on
SPARC. Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu.
Committed to mainline.
Ian
Index: gcc
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
Richard.
2016-10-12 Richard Biener
PR debug/77947
* cgraphunit.c (analyze_functions): Preserve cgraph nodes
function context.
* g++.dg/torture/pr77947.C: New testcase.
Index: gcc/cgraphunit.c
Hi Jeff,
On 10 October 2016 at 23:06, Jeff Law wrote:
>
>
> So if we have an equality conditional between A & B, we record into our
> const/copy tables A = B and B = A.
>
> This helps us discover some of the more obscure equivalences. But it also
> creates problems with an expression like
>
> A
On 10/12/16 09:43, Marek Polacek wrote:
ITYM lines 197 -> 203. I.e. remove the entire if that;s inside the 'mode ==
0' branch and make line 203 unconditional.
Yes, sorry for sloppy wording. I'm testing a patch.
Here's the patch I've tested (but not bootstrapped). As the incoming mode is
Hi,
> -Original Message-
> From: Matthew Fortune
> Sent: 19 September 2016 15:46
> To: Robert Suchanek; catherine_mo...@mentor.com
> Cc: gcc-patches@gcc.gnu.org
> Subject: RE: [PATCH 4/4] [MIPS] Add tests for MSA
>
> Hi Robert,
>
> Sorry for the long delay. Just a couple of cleanup bits
On 10.10.2016 23:06, Jeff Law wrote:
So if we have an equality conditional between A & B, we record into our
const/copy tables A = B and B = A.
This helps us discover some of the more obscure equivalences. But it also
creates problems with an expression like
A ^ B
Where we might cprop the fi
On Okt 12 2016, Nathan Sidwell wrote:
> @@ -182,9 +176,7 @@ gcov_open (const char *name, int mode)
>return 0;
> }
>
> - if (mode > 0)
> -gcov_var.mode = 1;
> - else if (mode == 0)
> + if (mode == 0)
> {
>struct stat st;
>
> @@ -194,21 +186,20 @@ gcov_open (con
On Wed, Oct 12, 2016 at 10:47:07AM -0400, Nathan Sidwell wrote:
> On 10/12/16 09:43, Marek Polacek wrote:
>
> > > ITYM lines 197 -> 203. I.e. remove the entire if that;s inside the 'mode
> > > ==
> > > 0' branch and make line 203 unconditional.
> >
> > Yes, sorry for sloppy wording. I'm testin
On 10/12/16 11:04, Andreas Schwab wrote:
Do we still need to call fstat? I don't think it can ever fail here.
You appear to be correct.
nathan
Hi,
As reported by Christophe Lyon, gcc.target/arm/movdi_movw test fails on big
endian targets. This is because on big endian targets the low bits of a 64bit
value would be in the highest numbered register of a pair rather than the lowest
numbered register as on little endian targets. This pat
On 12/10/16 16:21, Thomas Preudhomme wrote:
Hi,
As reported by Christophe Lyon, gcc.target/arm/movdi_movw test fails on big endian targets. This is because on big endian targets the low bits of a 64bit value would be in the highest numbered register of a pair rather than the lowest
numbered re
Sorry :-(
Here you are.
Cheers,
Thomas
On 12/10/16 16:25, Kyrill Tkachov wrote:
On 12/10/16 16:21, Thomas Preudhomme wrote:
Hi,
As reported by Christophe Lyon, gcc.target/arm/movdi_movw test fails on big
endian targets. This is because on big endian targets the low bits of a 64bit
value wo
I forgot that std::sample() was added to C++17, so it wasn't in our
status table. It is now.
I changed the testcase to use our iterator wrappers instead of
containers, which found some bugs. I intend to go through other tests
where I've used std::forward_list to get forward iterators, or stream
i
This patch to libgo copies the Go 1.7 runtime semaphore code into
libgo, basically replacing sema.goc (written in C) with sema.go
(writteh in Go).
This triggered a check in releaseSudog that g.param not nil, because
libgo uses the param field when starting a goroutine. Fixed by clearing
g->param
On Mon, Oct 03, 2016 at 01:48:21PM +, Segher Boessenkool wrote:
> This is the main substance of this patch series.
I forgot to update the changelog before, what I committed is:
* function.c (thread_prologue_and_epilogue_insns): Call
try_shrink_wrapping_separate. Compute the
On 10/10/16 12:15, Richard Biener wrote:
On Mon, 10 Oct 2016, Richard Biener wrote:
On Mon, 10 Oct 2016, Kyrill Tkachov wrote:
On 10/10/16 11:22, Richard Biener wrote:
On Mon, 10 Oct 2016, Kyrill Tkachov wrote:
Hi Richard,
As I mentioned, here is the patch applying to the main store merg
On 12/10/16 16:29, Thomas Preudhomme wrote:
Sorry :-(
Here you are.
Cheers,
Thomas
On 12/10/16 16:25, Kyrill Tkachov wrote:
On 12/10/16 16:21, Thomas Preudhomme wrote:
Hi,
As reported by Christophe Lyon, gcc.target/arm/movdi_movw test fails on big
endian targets. This is because on big e
On Wed, 12 Oct 2016, Richard Biener wrote:
> I'd say what applies to PA should apply equally well to the pdp11 and
> the alpha port ...
>
> But usually the question is just whether the port has a maintainer
> and/or whether it is
> a maintainance burden to keep it (say, last user of obsolete feat
On Wed, 12 Oct 2016, Martin Liška wrote:
> Last question is whether one can aggressively fold strcasecmp in a host
> compiler? Or are there any situations where results depends on locale?
There are the usual issues with Turkish locales having the uppercase
version of 'i' being 'İ' and the lower
On Wed, Sep 28, 2016 at 05:17:14PM +0100, James Greenhalgh wrote:
> On Wed, Sep 21, 2016 at 10:42:03AM +0100, James Greenhalgh wrote:
> > On Tue, Sep 13, 2016 at 10:31:28AM +0100, James Greenhalgh wrote:
> > > On Tue, Sep 06, 2016 at 10:19:50AM +0100, James Greenhalgh wrote:
> > > > This patch adds
On 12 October 2016 at 17:50, Kyrill Tkachov wrote:
>
> On 12/10/16 16:29, Thomas Preudhomme wrote:
>>
>> Sorry :-(
>>
>> Here you are.
>>
>> Cheers,
>>
>> Thomas
>>
>> On 12/10/16 16:25, Kyrill Tkachov wrote:
>>>
>>>
>>> On 12/10/16 16:21, Thomas Preudhomme wrote:
Hi,
As report
On 12/10/16 17:01, Christophe Lyon wrote:
On 12 October 2016 at 17:50, Kyrill Tkachov wrote:
On 12/10/16 16:29, Thomas Preudhomme wrote:
Sorry :-(
Here you are.
Cheers,
Thomas
On 12/10/16 16:25, Kyrill Tkachov wrote:
On 12/10/16 16:21, Thomas Preudhomme wrote:
Hi,
As reported by Ch
Hi,
This patch is a follow up of [1] which aims to have all memory model related
declarations in memmodel.h. To achieve that, this patch moves memory model
related declaration from coretypes.h into memmodel.h. Note that since memmodel.h
is now included from libgcc it needs to have a runtime li
On 10/12/2016 02:02 AM, Jakub Jelinek wrote:
On Wed, Oct 12, 2016 at 09:52:04AM +0200, Florian Weimer wrote:
dropping the alignment means that the padding before the lock member
vanishes. Consequently, we have just created a silent ABI change in
application code, which is a big no-no.
Sure, i
Hi all,
I have committed attached patch as obvious as r241071, because it just corrects
some indentation issues and a typo in a comment.
Bootstrapped and regtested ok on x86_64-linux/f23.
Regards,
Andre
--
Andre Vehreschild * Email: vehre ad gmx dot de
Index: gcc/fortran/ChangeLog
On 10/12/2016 06:43 AM, Kyrill Tkachov wrote:
On 12/10/16 11:18, Kyrill Tkachov wrote:
On 12/10/16 10:57, Kyrill Tkachov wrote:
On 11/10/16 20:19, Jakub Jelinek wrote:
On Tue, Oct 11, 2016 at 01:11:04PM -0600, Martin Sebor wrote:
Also, the pattern that starts with "/\+\+\+" looks like it's
On Wed, Oct 12, 2016 at 11:50:10AM +0200, Andre Vehreschild wrote:
> Ping!
>
> Updated patch with the comments gotten so far.
>
> Ok for trunk?
>
Looks good to me.
--
Steve
On Fri, 2016-10-07 at 15:58 +0200, Bernd Schmidt wrote:
> On 10/07/2016 03:26 PM, David Malcolm wrote:
> >
> > We could simply print the INSN_UID for CODE_LABELs; something like
> > this
> > (see the "(code_label 16" below):
>
> I think that should work.
>
> > You appear to have trimmed the idea
On 2016-10-12 12:14 PM, Jeff Law wrote:
On 10/12/2016 02:02 AM, Jakub Jelinek wrote:
On Wed, Oct 12, 2016 at 09:52:04AM +0200, Florian Weimer wrote:
dropping the alignment means that the padding before the lock member
vanishes. Consequently, we have just created a silent ABI change in
applicat
On 10/12/2016 07:48 PM, David Malcolm wrote:
This patch implements a "compact" mode for print_rtx_function,
implementing most of the ideas above.
Example of output can be seen here:
https://dmalcolm.fedorapeople.org/gcc/2016-10-12/test-switch-compact.rtl
which can be contrasted with the non-co
On Wed, Oct 12, 2016 at 7:28 AM, Ian Lance Taylor wrote:
> This patch to libgo by James Clarke fixes libgo for sparc64. The
> getrandom syscall was being ignored because the file was named
> "sparc". The clone syscall apparently needs special attention on
> SPARC. Bootstrapped and ran Go testsu
On 10/12/2016 06:14 PM, Jeff Law wrote:
If the issue is strictly limited to 32 bit hpux, then do we really care?
Can we just deprecate that platform and thus make the issue go away?
Are we talking about HP-XX or Linux on PA-RISC?
Thanks,
Florian
It doesn't make sense to warn about placement new of over-aligned
types; most occurrences are likely to be doing this in order to
provide properly aligned memory by allocating it first and then using
the standard non-allocating placement new.
Also, the discussion of -Waligned-new on HPPA led me to
On 2016-10-12 2:01 PM, Florian Weimer wrote:
On 10/12/2016 06:14 PM, Jeff Law wrote:
If the issue is strictly limited to 32 bit hpux, then do we really care?
Can we just deprecate that platform and thus make the issue go away?
Are we talking about HP-XX or Linux on PA-RISC?
The patch was int
This patch to the Go frontend and libgo copies the string code from
the Go 1.7 runtime. This mainly replaces some C code with Go code.
This adds compiler support for turning concatenating strings into a
call to a runtime function that takes the appropriate number of
arguments.
This renames some
On 10/12/16 11:04, Andreas Schwab wrote:
Do we still need to call fstat? I don't think it can ever fail here.
Update removing the fstat. Survived a profiled bootstrap, so I'll commit
tomorrow, unless there are further comments. Thanks for spotting this!
nathan
2016-10-12 Nathan Sidwel
Hi Richard,
On 12/10/16 23:24, Richard Biener wrote:
On Wed, Oct 12, 2016 at 8:56 AM, kugan
wrote:
Hi,
This patch uses get_ptr_nonnull in tree-vrp.
Bootstrapped and regression tested this with other patched without any
new regressions on x86_64-linux-gnu.
Is this OK for trunk?
Um. Doesn'
On 10/11/2016 10:14 PM, Bernd Schmidt wrote:
On 10/11/2016 04:23 PM, Denys Vlasenko wrote:
This is better than current behavior, but this is not what I want.
15-byte function does not need to be aligned to 16 bytes on a
machine with 128-byte L1I cachelines. It needs to be aligned to 128
bytes
Hi Jeff,
On 10.10.16 23:10, Jeff Law wrote:
On 10/10/2016 03:07 PM, Andreas Tobler wrote:
Hi all,
the attached patch brings support for the aarch64-*-freebsd* target.
Bootstraped and tested, results on the list. Not that many results due
to board instabilities I lack a cavium ;)
Ok for m
On 10/12/2016 08:55 AM, Joseph Myers wrote:
On Wed, 12 Oct 2016, Martin Liška wrote:
Last question is whether one can aggressively fold strcasecmp in a host
compiler? Or are there any situations where results depends on locale?
There are the usual issues with Turkish locales having the upperc
On 10/12/2016 10:17 AM, John David Anglin wrote:
> On 2016-10-12 9:48 AM, Jason Merrill wrote:
>> On Wed, Oct 12, 2016 at 4:02 AM, Jakub Jelinek wrote:
>>> On Wed, Oct 12, 2016 at 09:52:04AM +0200, Florian Weimer wrote:
dropping the alignment means that the padding before the lock member
On Wed, 12 Oct 2016, Thomas Preudhomme wrote:
> This patch is a follow up of [1] which aims to have all memory model related
> declarations in memmodel.h. To achieve that, this patch moves memory model
> related declaration from coretypes.h into memmodel.h. Note that since
> memmodel.h is now incl
* Claudiu Zissulescu [2016-10-10 15:26:47
+0200]:
> Hi Andrew,
>
> This is updated patch of the original sent to mailing list some while ago.
>
> What is new:
> - Do not use MULTILIB_REUSE as its semantic changed, and the old one was
> causing issues while building.
> - Update invok
On Wed, 2016-10-12 at 19:31 +0200, Bernd Schmidt wrote:
> On 10/12/2016 07:48 PM, David Malcolm wrote:
> > This patch implements a "compact" mode for print_rtx_function,
> > implementing most of the ideas above.
> >
> > Example of output can be seen here:
> > https://dmalcolm.fedorapeople.org/gc
On Wed, 2016-10-12 at 19:31 +0200, Bernd Schmidt wrote:
> On 10/12/2016 07:48 PM, David Malcolm wrote:
[...snip...]
> > I think the only remaining item from our discussion above is what
> > to do
> > about the numbering of pseudos in the dumps (currently it just
> > prints the regno
> > unmodifie
On 10/10/2016 23:01, Tim Song wrote:
Trying again...with a few edits.
On Mon, Oct 10, 2016 at 3:24 PM, François Dumont
wrote:
@@ -602,24 +612,32 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
struct _Rb_tree_impl : public _Node_allocator
{
_Key_compare _M_key_compare;
- _Rb_tree
2016-09-27 Denys Vlasenko
* config/i386/i386-common.c (ix86_handle_option): Remove support
for obsolete -malign-loops, -malign-jumps and -malign-functions
options.
* config/i386/i386.opt: Likewise.
Index: gcc/common/config/i386/i386-common.c
These patches are for this bug:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66240
"RFE: extend -falign-xyz syntax"
The test program:
int g();
int f(int i) {
i *= 3;
while (--i > 100) {
L1:if (g()) goto L1;
if (g()) goto L2;
}
return i
This change drops forced alignment to 8 if requested alignment is higher
than 8: before the patch, -falign-functions=9 was generating
.p2align 4,,8
.p2align 3
which means: "align to 16 if the skip is 8 bytes or less; else align to 8".
After this change, ".p2align 3" is not emitted
falign-functions=N is too simplistic.
Ingo Molnar ran some tests and it seems that on latest x86 CPUs, 64-byte
alignment
of functions runs fastest (he tried many other possibilites):
this way, after a call CPU can fetch a lot of insns in the first cacheline fill.
However, developers are less tha
There is a missing big-endian correction when types smaller than a word are
passed through va_arg without promotion like _Complex char.
Tested on visium-elf, applied on the mainline.
2016-10-12 Eric Botcazou
* config/visium/visium.c (visium_gimplify_va_arg): Emit a big-endian
On Wed, Oct 12, 2016 at 4:36 PM, François Dumont wrote:
> On 10/10/2016 23:01, Tim Song wrote:
>>
>> Trying again...with a few edits.
>>
>>> On Mon, Oct 10, 2016 at 3:24 PM, François Dumont
>>> wrote:
>>>
>>> @@ -602,24 +612,32 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
>>> struct _Rb_tree_imp
Sorry, haven't had time to read the full series yet, but:
David Malcolm writes:
> On Wed, 2016-10-05 at 17:51 +0200, Bernd Schmidt wrote:
>> On 10/05/2016 06:14 PM, David Malcolm wrote:
>> > The selftests for the RTL frontend require supporting multiple
>> > reader instances being alive one after
Hi!
Seems 2 functions in varasm.c just use TREE_PUBLIC on LABEL_DECLs together
with other kinds of decls, but as TREE_PUBLIC on LABEL_DECLs means now
something different, it breaks badly.
While I could change those 2 functions in varasm.c, I'm afraid other
functions might be doing something simila
Hi!
PR77957 is likely a rs6000 backend bug where a useless memory load causes
.LCTOC0 undefined reference in the end at -O0 and as such should be fixed,
but I think it is completely unnecessary to create those loads at all
if we know we are going to ignore it in the stack_protect_{set,test}
patter
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77937 reports an ICE in SLSR
where a POINTER_PLUS_EXPR occurs with a candidate increment of -1. This
is supposed to be prevented by code in analyze_increments, since replacement
of such a candidate is not guaranteed to be profitable. The test for this
On Wed, Oct 12, 2016 at 10:43 AM, Ian Lance Taylor wrote:
> On Wed, Oct 12, 2016 at 7:28 AM, Ian Lance Taylor wrote:
>> This patch to libgo by James Clarke fixes libgo for sparc64. The
>> getrandom syscall was being ignored because the file was named
>> "sparc". The clone syscall apparently nee
On Wed, Oct 12, 2016 at 8:03 PM, Andrew Pinski wrote:
> On Wed, Oct 12, 2016 at 10:43 AM, Ian Lance Taylor wrote:
>> On Wed, Oct 12, 2016 at 7:28 AM, Ian Lance Taylor wrote:
>>> This patch to libgo by James Clarke fixes libgo for sparc64. The
>>> getrandom syscall was being ignored because the
Hi Richard,
On 13/10/16 05:53, kugan wrote:
Hi Richard,
On 12/10/16 23:24, Richard Biener wrote:
On Wed, Oct 12, 2016 at 8:56 AM, kugan
wrote:
Hi,
This patch uses get_ptr_nonnull in tree-vrp.
Bootstrapped and regression tested this with other patched without any
new regressions on x86_64-
Hi Richard,
what does this try to do? Preserve info VRP computed across PTA?
I think we didn't yet sort out the nonlocal/escaped vs. null handling properly
(or how PTA should handle get_ptr_nonnull). The way you are using it
asks for pt.null to be orthogonal to nonlocal/escaped and thus havi
On 2016.10.12 at 20:14 -0500, Bill Schmidt wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77937 reports an ICE in SLSR
> where a POINTER_PLUS_EXPR occurs with a candidate increment of -1. This
> is supposed to be prevented by code in analyze_increments, since replacement
> of such a candida
On Wed, Oct 12, 2016 at 9:20 PM, Ian Lance Taylor wrote:
> On Wed, Oct 12, 2016 at 8:03 PM, Andrew Pinski wrote:
>> On Wed, Oct 12, 2016 at 10:43 AM, Ian Lance Taylor wrote:
>>> On Wed, Oct 12, 2016 at 7:28 AM, Ian Lance Taylor wrote:
This patch to libgo by James Clarke fixes libgo for spa
Bernd Schmidt writes:
> On 09/16/2016 09:02 PM, Senthil Kumar Selvaraj wrote:
>> Does this make sense? I ran a reg test for the avr target with a
>> slightly older version of this patch, it did not show any regressions.
>> If this is the right fix, I'll make sure to run reg tests on x86_64
101 - 172 of 172 matches
Mail list logo
