Ping^2?
Thanks,
Kugan
On 21 July 2017 at 20:12, Kugan Vivekanandarajah
wrote:
> Ping ?
>
> Thanks,
> Kugan
>
> On 27 June 2017 at 11:20, Kugan Vivekanandarajah
> wrote:
>> https://gcc.gnu.org/ml/gcc-patches/2016-03/msg00614.html added this
>> workaround to get kernel building with when TARGET_
We were wrongly checking for nullptr_node rather than nullptr_type.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit 325d154928a702116006f1ca40806cee600d6a8b
Author: Jason Merrill
Date: Thu Aug 10 22:05:38 2017 -0700
PR c++/81671 - nullptr_t template parameter
Hi,
Please consider this as a personal reminder to review the patch
at following link and let me know your comments on the same.
https://gcc.gnu.org/ml/gcc-patches/2017-07/msg01634.html
Thanks,
Naveen
Hi,
Please consider this as a personal reminder to review the patch
at following link and let me know your comments on the same.
https://gcc.gnu.org/ml/gcc-patches/2017-07/msg01529.html
Thanks,
Naveen
Hi,
Please consider this as a personal reminder to review the patch
at following link and let me know your comments on the same.
https://gcc.gnu.org/ml/gcc-patches/2017-03/msg00505.html
Thanks,
Naveen
It is possible when using out-of-line register saves or store multiple
to save some registers unnecessarily, for example one reg in the block
saved might be unused. We don't need to emit eh_frame info for those
registers as that just bloats the eh_frame info, and also can result
in an ICE when shr
rs6000_reg_live_or_pic_offset_p is just save_reg_p with special
handling for the pic register and eh_return. This merge also
simplifies the eh_return handling. The intent of
https://gcc.gnu.org/ml/gcc-patches/2010-09/msg01838.html was to say
the PIC reg needed to be saved for eh_return, not all g
As noted in fixed_reg_p comment
/* Return whether REG is a global user reg or has been specifed by
-ffixed-REG. We should not restore these, and so cannot use
lmw or out-of-line restore functions if there are any. We also
can't save them (well, emit frame notes for them), because frame
These need to match the gnu-user.h definitions to support
--enable-default-pie. Otherwise we end up linking the wrong startup
files when defaulting to PIE.
I've just copied the HAVE_LD_PIE variants as we don't need the
!HAVE_LD_PIE variant. (In fact, gnu-user.h doesn't need them either.)
Bootst
On 26/07/17 23:06 +0100, Jonathan Wakely wrote:
On 26/07/17 20:14 +0200, Paolo Carlini wrote:
Hi again,
On 26/07/2017 16:27, Paolo Carlini wrote:
Hi,
On 26/07/2017 16:21, Andreas Schwab wrote:
ERROR: 27_io/basic_fstream/53984.cc: unknown dg option:
dg-require-file-io 18 {} for " dg-require-f
2017-08-10 10:40 GMT+03:00 Martin Liška :
> Hello.
>
> In order to prevent the ICE, CHKP should not isntrument variables of void
> type.
Hi,
There was another thread for this PR where I proposed a way to handle such vars
via size relocations. But there was no feedback in that thread for two
mont
On Thu, 10 Aug 2017, Ximin Luo wrote:
> Normally, system-wide CFLAGS etc are a static expression of policy. What I
> mean
> by that is, writing logic to determine CFLAGS for particular package, would
> "look like" the actual wording of that policy. So for example, "all packages
> should have debu
On Thu, 10 Aug 2017, Jackson Woodruff wrote:
> > We also change:
> >
> > x / (- y) -> (-x) / y
> >
> > Which requires -fno-trapping-math.
I don't see why that requires -fno-trapping-math. The exceptions should
be identical from both variants, as should the result, as far as defined
by C or
On Wed, 9 Aug 2017, Martin Sebor wrote:
> The problem isn't that the declarations aren't merged at the call
> site but rather that the middle-end gives const precedence over
> pure so when both attributes are provided the former wins.
But that precedence is correct. Any function with the semanti
Hi,
This continues the cleanup of diagnostic messages in the rs6000 back end. The
primary focus is to make sure that we use quoted strings with %qs, %<, %> as
appropriate, and that option strings are separated from translatable strings
to make things easier on the internationalization folks, as r
Hi all,
One issue that we keep encountering on aarch64 is GCC not making good use of
the flag-setting arithmetic instructions
like ADDS, SUBS, ANDS etc. that perform an arithmetic operation and compare the
result against zero.
They are represented in a fairly standard way in the backend as PARAL
On Thu, Aug 10, 2017 at 8:32 PM, Uros Bizjak wrote:
> ... and use address spaces to load boundary value from TLS block.
>
> The patch removes special handling for boundary value location.
I have renamed ix86_split_stack_boundary to ix86_split_stack_guard
(and added missing function comment), so t
Yury Gribov:
> On Thu, Aug 3, 2017 at 12:45 PM, Ximin Luo wrote:
>> Yury Gribov:
>>> [..]
>>>
>>> Shouldn't -fdebug-prefix-map be updated to use the same syntax as
>>> BUILD_PATH_PREFIX_MAP?
>>>
>>
>> -fdebug-prefix-map is a CLI option and can be given multiple times, each
>> flag given is in th
Jakub Jelinek:
> On Fri, Aug 04, 2017 at 08:32:33AM -0400, Matthias Klose wrote:
GCC already supports a similar environment variable SOURCE_DATE_EPOCH,
which was accepted about 2 years ago in a patch written by one of our GSoC
students. We are not planning any more environment vari
Yury Gribov:
> [..]
>
> In general any distro provides some way to set default parameters for
> every package. Adding hacks to compiler to work around limitations of
> particular build system does not sound right.
>
> Here's a relevant discussion from binutils ML:
> https://sourceware.org/ml/bin
On Thu, Aug 10, 2017 at 12:13 AM, Markus Trippelsdorf
wrote:
> On 2017.08.09 at 14:30 -0400, Jason Merrill wrote:
>> The issue here is that we try to determine the EH specification of
>> B::C::C() from within SFINAE context, and we can't determine it yet
>> because the NSDMI for B::C::i hasn't bee
On 07/14/2017 01:35 AM, Martin Liška wrote:
On 05/01/2017 09:13 PM, Jason Merrill wrote:
On Wed, Apr 26, 2017 at 6:58 AM, Martin Liška wrote:
On 04/25/2017 01:58 PM, Jakub Jelinek wrote:
On Tue, Apr 25, 2017 at 01:48:05PM +0200, Martin Liška wrote:
Hello.
This is patch that was originally i
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 zero (that's a zero-length
+array likely at the end of a struct). *
Jon's earlier patch expanded our existing implicit move semantics
support to allow other types, but this testcase demonstrates a hole in
that support: it didn't affect function template argument deduction.
Rather than try to tweak deduction as well as reference binding, this
patch actually does ove
My new warning triggered here and said "bitwise comparison always evaluates to
true" and I believe it's right: GOVD_WRITTEN = 131072 which is 10... in
binary, so n->value & GOVD_WRITTEN can never be 1; I suppose 0 was meant to
be used here instead. Too bad Jakub's away, so he can't confirm.
B
... and use address spaces to load boundary value from TLS block.
The patch removes special handling for boundary value location.
2017-08-10 Uros Bizjak
* config/i386/i386-protos.h (ix86_split_stack_boundary): New prototype.
* config/i386/i386.c (ix86_split_stack_boundary): New functi
On August 10, 2017 3:37:55 PM GMT+02:00, Richard Sandiford
wrote:
>The second loop in the testcase only vectorises if we can reverse
>a vector and if aligned loads aren't required.
>
>Sanity-checked on aarch64-linux-gnu, x86_64-linux-gnu and
>powerpc64le-linux-gnu (although all three were unaffec
I would like to modify gcc.target/aarch64/long_branch_1.c to no longer
look for an Ltb label. After a patch to c-typeck.c to add a predict
statement to GOTO statements, GCC no longer generates one of the types
of long branch that this test is checking for.
I tried modifying the test and creating
Hi,
The attached patch adds a new switch -fftz-math which makes certain
optimizations
assume that "flush to zero" behavior of denormal inputs and outputs is
not an optimization
hint, but required behavior for semantical correctness.
The need for this was initiated by HSAIL (BRIG). With HSAIL, flu
Hi,
A new vendor CFA DW_CFA_AARCH64_negate_ra_state was introduced for ARMv8.3-A
return address signing, it is multiplexing DW_CFA_GNU_window_save in CFA vendor
extension space.
This patch adds necessary code to make it available to external, the GDB
patch (https://sourceware.org/ml/gdb-patc
When MMX is disabled, MMX registers aren't available. We shouldn't
allow builtins with MMX registers when MMX registers aren't available.
This applies to MMX and 3DNow builtins as well as SSE builtins with
MMX registers.
Also we should always declare all builtins and ix86_expand_builtin
will give
On 07/06/17 12:38, Tamar Christina wrote:
> Hi All,
>
> This patch allows the inlining of lrint when -fno-math-errno
> assuming that errno does not need to be set when the rounded value
> is not representable as a long.
>
turns out emitting frintx+fcvtzs is wrong for ilp32
because spurious inexa
Hi all,
The patch implements the some of the division optimizations discussed in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71026 .
We now reassociate (as discussed in the bug report):
x / (y * y) -> x * (1 / y) * (1 / y)
If it is reasonable to do so. This is done with
-funsafe-math-opt
And have now attached that patch.
Jackson
On 08/10/2017 03:09 PM, Jackson Woodruff wrote:
Hi all,
The patch implements the division opitmizations discussed in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71026 .
The implemented change differs slightly from the
proposed one in that we re-asso
I find them strange too... But as you say, they are needed for old
code, and some such code bases are quite large and/or have
uncooperative users or maintainers.
Committed with %qs throughout, thanks for review.
---
Fritz Reese
On Tue, Aug 1, 2017 at 11:29 AM, Thomas Koenig wrote:
> Hi Fritz,
>
Hi all,
The patch implements the division opitmizations discussed in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71026 .
The implemented change differs slightly from the
proposed one in that we re-associate:
C / x comparison 0.0 -> x comparison' 0.0
Where C is any constant and comparison'
Yes I did. Committed, thanks.
---
Fritz Reese
On Tue, Aug 1, 2017 at 11:11 AM, Thomas Koenig wrote:
> Hi Fritz,
>
>> This is a simple patch. The original intent was for -fdec to set
>> -fd-lines-as-comments by default if flag_d_lines was unspecified by
>> the user. However, currently flag_d_lin
> On 06/30/2017 10:47 AM, Martin Liška wrote:
> >Hello.
> >
> >Following patch does refactoring of make_resolver_func where ifunc
> >alias and resolver were probably confused.
> >
> >Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
> >i386.exp tests work on x86_64-linux-gn
On Thu, Aug 10, 2017 at 08:27:17AM -0500, Will Schmidt wrote:
> A testcase coverage issue and an obvious typo fix.
>
> Mostly obvious,.. OK for trunk?
Yes; one comment:
> diff --git a/gcc/testsuite/gcc.target/powerpc/fold-vec-pack-longlong.c
> b/gcc/testsuite/gcc.target/powerpc/fold-vec-pack-
On Thu, Aug 10, 2017 at 12:39 AM, Uros Bizjak wrote:
> On Thu, Aug 10, 2017 at 9:09 AM, Richard Sandiford
> wrote:
>> "H.J. Lu" writes:
>>> On Wed, Aug 9, 2017 at 10:28 AM, H.J. Lu wrote:
On Wed, Aug 9, 2017 at 8:26 AM, Andi Kleen wrote:
>> This must be much more specific. How does i
> On 07/31/2017 11:57 AM, Yuri Gribov wrote:
> > On Mon, Jul 31, 2017 at 9:04 AM, Martin Liška wrote:
> >> Hi.
> >>
> >> Doing the transformation suggested by Honza.
> >>
> >> Patch can bootstrap on ppc64le-redhat-linux and x86_64-linux-gnu and
> >> survives regression tests.
> >> And I also veri
On Thu, Aug 10, 2017 at 02:17:40PM +0930, Alan Modra wrote:
> > > Ick, looks like papering over the real problem to me, and will no
> > > doubt cause -Os size regressions.
> >
> > I think it is very directly solving the real problem. It isn't likely
> > to cause size regressions (look how long it
> > - /* If callee has no option attributes, then it is ok to inline. */
> > - if (!callee_tree)
> > + /* If callee has no option attributes (or default),
> > + then it is ok to inline. */
> > + if (!callee_tree || callee_tree == target_option_default_node)
>
> >>
The second loop in the testcase only vectorises if we can reverse
a vector and if aligned loads aren't required.
Sanity-checked on aarch64-linux-gnu, x86_64-linux-gnu and
powerpc64le-linux-gnu (although all three were unaffected).
OK to install?
Thanks,
Richard
2017-08-10 Richard Sandiford
Hi,
A testcase coverage issue and an obvious typo fix.
Mostly obvious,.. OK for trunk?
Thanks,
-Will
[gcc/testsuite]
2017-08-10 Will Schmidt
* gcc.target/powerpc/fold-vec-msum-short.c: Fix typo.
* gcc.target/powerpc/fold-vec/pack-longlong.c: Mark for 64-bit only.
diff --
Hi all,
This patch changes patterns in aarch64-simd.md to replace
moviv0.4s, 0
strq0, [x0, 16]
With:
stp xzr, xzr, [x0, 16]
When we are storing zeros to vectors like this:
void f(uint32x4_t *p) {
uint32x4_t x = { 0, 0, 0, 0};
p[1] = x;
}
Bootstrapped
On Wed, 9 Aug 2017, Jeff Law wrote:
> >> The _5th macro isn't that bad either, appart from using reserved namespace
> >> identifiers (it really should be something like qsort_5th and the arguments
> >> shouldn't start with underscores).
> >
> > I didn't understand what Jeff found "ugly" about it;
On 01/08/17 15:31, Olivier Hainque wrote:
> Hello,
>
> On top of previous changes reworking the arm-vxworks support
>
> https://gcc.gnu.org/ml/gcc-patches/2017-08/msg00085.html
> https://gcc.gnu.org/ml/gcc-patches/2017-08/msg00075.html
> https://gcc.gnu.org/ml/gcc-patches/2017-08/msg00078.h
Hi Tom!
On Thu, 3 Aug 2017 13:23:16 +0200, Tom de Vries wrote:
> [ was: Re: [testsuite, PR81662, committed] Skip
> fpatchable-function-entry tests for nvptx ]
>
> On 08/03/2017 09:17 AM, Tom de Vries wrote:
> > fpatchable-function-entry requires nop, which nvptx does not have.
Generally, shoul
Hi Thomas,
It looks fine to me. OK for trunk.
Thanks
Paul
PS What about PR34640 ?
On 9 August 2017 at 20:44, Thomas Koenig wrote:
> Am 02.08.2017 um 15:19 schrieb Thomas Koenig:
>>
>> the attached patch is a bit smaller than it looks, because most of
>> it is due to reformatting a large
With -m32 intptr_t can be just 'int', not 'long int', so accept that too.
Tested on x86_64-linux, applying to trunk.
2017-08-10 Marek Polacek
* objc.dg/proto-lossage-4.m: Accept int/long int as intptr_t.
diff --git gcc/testsuite/objc.dg/proto-lossage-4.m
gcc/testsuite/objc.dg/proto-
PING^1
On 05/30/2017 02:52 PM, Richard Biener wrote:
>
> This patch (in the attempt to find a place to put a link to
> http://gcc.opensuse.org/gcc_bugzilla/ to) adds a list of suggestions
> where to look for work in bugzilla.
>
> Ok?
>
> Thanks,
> Richard.
>
> 2017-05-30 Richard Biener
>
>
ot; "" { target *-*-* } .-1 } */
> >
> >receiver += [(Obj *)objrcvr2 anotherValue];
> >
>
> FAIL: objc.dg/proto-lossage-4.m -fgnu-runtime (test for warnings, line 30)
> FAIL: objc.dg/proto-lossage-4.m -fgnu-runtime (test for warnings, line 36)
On Thu, Aug 10, 2017 at 09:35:07AM +0200, Andreas Schwab wrote:
> FAIL: gcc.dg/compare2.c case 20 (test for warnings, line 49)
> FAIL: gcc.dg/compare2.c case 24 (test for warnings, line 57)
> FAIL: gcc.dg/compare2.c (test for excess errors)
> Excess errors:
> /usr/local/gcc/g
Not sure how I missed this, but a few dg-warning and dg-bogus need updating.
Tested on x86_64-linux and ppc64le-linux, applying to trunk.
2017-08-10 Marek Polacek
PR testsuite/81784
* gcc.dg/compare2.c: Update dg-bogus and dg-warning.
diff --git gcc/testsuite/gcc.dg/compare2.
t; integer from pointer without a cast" "" { target *-*-* } .-1 } */
>
>receiver += [(Obj *)objrcvr2 anotherValue];
>
FAIL: objc.dg/proto-lossage-4.m -fgnu-runtime (test for warnings, line 30)
FAIL: objc.dg/proto-lossage-4.m -fgnu-runtime (test for warnings, line 3
PING^2
On 07/27/2017 02:56 PM, Martin Liška wrote:
> PING^1
>
> On 07/14/2017 10:35 AM, Martin Liška wrote:
>> On 05/01/2017 09:13 PM, Jason Merrill wrote:
>>> On Wed, Apr 26, 2017 at 6:58 AM, Martin Liška wrote:
On 04/25/2017 01:58 PM, Jakub Jelinek wrote:
> On Tue, Apr 25, 2017 at 01:
On 08/02/2017 01:51 PM, Richard Biener wrote:
> On Wed, Aug 2, 2017 at 1:20 PM, Martin Liška wrote:
>> Hello.
>>
>> After some discussions with Honza, I've decided to convert current code in
>> stmt.c that
>> is responsible for switch expansion. More precisely, I would like to convert
>> the cod
Hello.
In order to prevent the ICE, CHKP should not isntrument variables of void type.
Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
Ready to be installed?
Martin
gcc/ChangeLog:
2017-08-09 Martin Liska
PR tree-opt/79987
* tree-chkp.c (chkp_get_b
On Thu, Aug 10, 2017 at 9:09 AM, Richard Sandiford
wrote:
> "H.J. Lu" writes:
>> On Wed, Aug 9, 2017 at 10:28 AM, H.J. Lu wrote:
>>> On Wed, Aug 9, 2017 at 8:26 AM, Andi Kleen wrote:
> This must be much more specific. How does it impact:
>
> 1. LTO
> 2. Function inlining.
>
FAIL: gcc.dg/compare2.c case 20 (test for warnings, line 49)
FAIL: gcc.dg/compare2.c case 24 (test for warnings, line 57)
FAIL: gcc.dg/compare2.c (test for excess errors)
Excess errors:
/usr/local/gcc/gcc-20170810/gcc/testsuite/gcc.dg/compare2.c:49:12: warning:
operand of ?: changes signedness
On August 10, 2017 7:26:33 AM GMT+02:00, Jeff Law wrote:
>On 08/06/2017 02:07 PM, Martin Sebor wrote:
>> Part 3 of the series contains the meat of the patch: the new
>> -Wstringop-truncation option, and enhancements to -Wstringop-
>> overflow, and -Wpointer-sizeof-memaccess to detect misuses of
>>
"H.J. Lu" writes:
> On Wed, Aug 9, 2017 at 10:28 AM, H.J. Lu wrote:
>> On Wed, Aug 9, 2017 at 8:26 AM, Andi Kleen wrote:
This must be much more specific. How does it impact:
1. LTO
2. Function inlining.
3. Partial function inlining.
4. Shrink-wrapping.
An
On 2017.08.09 at 14:30 -0400, Jason Merrill wrote:
> The issue here is that we try to determine the EH specification of
> B::C::C() from within SFINAE context, and we can't determine it yet
> because the NSDMI for B::C::i hasn't been parsed yet. This patch
> allows that determination to fail quiet
64 matches
Mail list logo
