On 2017.01.22 at 16:53 -0700, Martin Sebor wrote:
> This is the last patch in the series. It adds logic to handle
> non-constant width and precision with range information to help
> reduce both false positives false negatives. The patch replaces
> the scalar width and precision with two element a
Hi Martin,
> On 01/24/2017 02:37 AM, Markus Trippelsdorf wrote:
>> MPFR_RNDx was introduced in MPFR 3.0.0. Since the minimal version that
>> gcc checks for is 2.4.0, this leads to a build failure.
>>
>> The fix is straightforward.
>>
>> Tested on x86_64-pc-linux-gnu. Committed to trunk as obvious.
cpplib-7.1-b20170101.sr.po.gz
Description: Binary data
The Translation Project robot, in the
name of your translation coordinator.
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'cpplib' has been submitted
by the Serbian team of translators. The file is available at:
http://translationproject.org/latest/cpplib/sr.po
(This file, 'cpplib-7.1-b20170101
On Oct 19, 2016, Alexandre Oliva wrote:
> On Sep 23, 2016, Alexandre Oliva wrote:
>> On Aug 27, 2016, Alexandre Oliva wrote:
>>> Output DWARFv5+ DW_AT_alignment for non-default alignment of
>>> variables, fields and types.
>>> Regstrapped on x86_64-linux-gnu and i686-linux-gnu. Ok to install?
On Oct 19, 2016, Alexandre Oliva wrote:
> On Sep 23, 2016, Alexandre Oliva wrote:
>> On Aug 30, 2016, Alexandre Oliva wrote:
>>> Handling non-template friends is kind of easy, [...]
>> Regstrapped on x86_64-linux-gnu and i686-linux-gnu, I'd failed to
>> mention.
>> Ping?
> Ping? (conflicts
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'cpplib' has been submitted
by the Serbian team of translators. The file is available at:
http://translationproject.org/latest/cpplib/sr.po
(This file, 'cpplib-7.1-b20170101
cpplib-7.1-b20170101.sr.po.gz
Description: Binary data
The Translation Project robot, in the
name of your translation coordinator.
I committed the patch below to clean up the "mess."
Thanks
Martin
Index: gcc/gimple-ssa-sprintf.c
===
--- gcc/gimple-ssa-sprintf.c(revision 244957)
+++ gcc/gimple-ssa-sprintf.c(working copy)
@@ -1686,20 +1686,10 @@ format_fl
Here are the incremental changes that, together, address all of your
feedback (thanks!), but separated in logically-related patches. In a
separate message, I'll post an updated, consolidated patch.
Rename ansi_*opname; export cp_literal_operator_id
diff --git a/gcc/cp/call.c b/gcc/cp/call.c
ind
On Thu, Jan 26, 2017 at 5:19 PM, Segher Boessenkool
wrote:
> On Thu, Jan 26, 2017 at 05:00:44PM -0800, Andrew Pinski wrote:
>> On Thu, Jan 26, 2017 at 4:38 PM, Segher Boessenkool
>> wrote:
>> > Scheduling should never move very expensive instructions to places they
>> > are executed more frequent
On Thu, Jan 26, 2017 at 05:00:44PM -0800, Andrew Pinski wrote:
> On Thu, Jan 26, 2017 at 4:38 PM, Segher Boessenkool
> wrote:
> > Scheduling should never move very expensive instructions to places they
> > are executed more frequently. This patch fixes that, reducing the
> > execution time of c-r
On Thu, Jan 26, 2017 at 3:17 PM, Martin Sebor wrote:
>> Hi,
>>
>> With this patch all my builds for aarch64/arm failed:
>> /gcc/gimple-ssa-sprintf.c: In function
>> ‘::fmtresult::format_floating(const::direc
>> tive&, tree_node*)’:
>> /gcc/gimple-ssa-sprintf.c:1643: error: ‘XFmode’ was not declare
On Thu, Jan 26, 2017 at 4:38 PM, Segher Boessenkool
wrote:
> Scheduling should never move very expensive instructions to places they
> are executed more frequently. This patch fixes that, reducing the
> execution time of c-ray by over 40% (I tested on a BE Power7 system).
>
> Is there some existi
On Thu, Jan 26, 2017 at 05:31:16PM -0600, Bill Schmidt wrote:
> > So for older targets it used to run the final, but not after the patch; and
> > for newer targets it used to not run it, but it does after the patch? So
> > it is meant to be two changes?
>
> Correct, I forgot to point out that for
Scheduling should never move very expensive instructions to places they
are executed more frequently. This patch fixes that, reducing the
execution time of c-ray by over 40% (I tested on a BE Power7 system).
Is there some existing way to test for "very expensive insn" or "very
expensive insn we s
On 01/26/2017 04:17 PM, Martin Sebor wrote:
Hi,
With this patch all my builds for aarch64/arm failed:
/gcc/gimple-ssa-sprintf.c: In function
‘::fmtresult::format_floating(const::direc
tive&, tree_node*)’:
/gcc/gimple-ssa-sprintf.c:1643: error: ‘XFmode’ was not declared in
this scope
Is this fix
> On Jan 26, 2017, at 5:15 PM, Segher Boessenkool
> wrote:
>
> On Thu, Jan 26, 2017 at 04:36:31PM -0600, Bill Schmidt wrote:
-/* { dg-final { scan-tree-dump-times "vectorized 1 loops" 1 "vect" {
target { ! vect_no_align } } } } */
-/* { dg-final { scan-tree-dump-times "vectoriz
Hi,
With this patch all my builds for aarch64/arm failed:
/gcc/gimple-ssa-sprintf.c: In function
‘::fmtresult::format_floating(const::direc
tive&, tree_node*)’:
/gcc/gimple-ssa-sprintf.c:1643: error: ‘XFmode’ was not declared in this scope
Is this fixed later in the series?
It isn't. I just r
On Thu, Jan 26, 2017 at 04:36:31PM -0600, Bill Schmidt wrote:
> >> -/* { dg-final { scan-tree-dump-times "vectorized 1 loops" 1 "vect" {
> >> target { ! vect_no_align } } } } */
> >> -/* { dg-final { scan-tree-dump-times "vectorizing stmts using SLP" 1
> >> "vect" { target { ! vect_no_align } }
On Thu, Jan 26, 2017 at 03:14:47PM -0600, Bill Schmidt wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65484 identifies an
> issue whether g++.dg/vect/pr36648.cc fails on older POWER hardware.
> This is due to a decision made in November 2010 to include the
> flag -mno-allow-movmisalign in ch
> On Jan 26, 2017, at 4:29 PM, Segher Boessenkool
> wrote:
>
> On Thu, Jan 26, 2017 at 03:14:47PM -0600, Bill Schmidt wrote:
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65484 identifies an
>> issue whether g++.dg/vect/pr36648.cc fails on older POWER hardware.
>> This is due to a decision ma
On 26 January 2017 at 00:31, Jeff Law wrote:
> On 01/22/2017 04:53 PM, Martin Sebor wrote:
>>
>> The attached patch adds the concept of likely and unlikely results
>> of formatted functions to improve the quality of diagnostics (reduce
>> false positives and negatives) while at the same time allow
OK.
On Thu, Jan 19, 2017 at 10:32 AM, Jakub Jelinek wrote:
> Hi!
>
> This is on top of the PR78835 patch I've posted yesterday.
> We ICE on the following testcase reduced from libstdc++ ios_failure.cc.
> If there are nested comdat types, as B (outer type) and A (inner type) in the
> testcase, we
OK.
On Wed, Jan 18, 2017 at 7:32 AM, Jakub Jelinek wrote:
> Hi!
>
> The following patch fixes ICE with -fdebug-types-section on the following
> testcase. We prune DIEs in the main CU for methods in a class that is
> moved into .debug_types section, because we don't see any uses of those
> in the
Hi,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65484 identifies an
issue whether g++.dg/vect/pr36648.cc fails on older POWER hardware.
This is due to a decision made in November 2010 to include the
flag -mno-allow-movmisalign in check_vect_support_and_set_flags,
which governs the vectorizer test
Hi,
This patch enables -fprefetch-loop-arrays for -mcpu=thunderxt88 and
-mcpu=thunderxt88p1. I filled out the tuning structures for both
thunderx and thunderx2t99. No other core current enables software
prefetching so I set them to 0 which does not change the default
parameters.
OK? Bootstrap
On Thu, Jan 26, 2017 at 09:42:39PM +0100, Dominik Vogt wrote:
> gcc/ChangeLog-pr79240
>
> PR target/79240
> * config/s390/s390.md ("*rsbg__srl_bitmask")
> ("*rsbg__sll_bitmask")
> ("*extzv__srl")
> ("*extzv__sll"):
> Use contiguous_bitmask_nowrap_operand
Missin
On Thu, Jan 26, 2017 at 09:44:14PM +0100, Thomas Schwinge wrote:
> > The following patch should fix that, ok for trunk?
>
> Looks good to me (but I can't approve it, as you know).
Sure, I know.
>
> One additional comment:
>
> > --- gcc/testsuite/g++.dg/asan/pr69276.C.jj 2016-02-04 23:14:18.000
The attached patch uses macros from hwint.h in the s390 backend
where possible.
Bootstrapped and regression tested on a zEC12 with s390x biarch
and s390.
Ciao
Dominik ^_^ ^_^
--
Dominik Vogt
IBM Germany
gcc/ChangeLog-macros
* config/s390/predicates.md ("larl_operand"): Use macros fr
Hi!
On Thu, 26 Jan 2017 11:54:07 +0100, Jakub Jelinek wrote:
> On Thu, Jan 26, 2017 at 09:57:14AM +0100, Thomas Schwinge wrote:
> > On Mon, 23 Jan 2017 10:19:33 +0100, Martin Liška wrote:
> > > --- a/gcc/testsuite/gcc.dg/asan/use-after-scope-3.c
> > > +++ b/gcc/testsuite/gcc.dg/asan/use-after-sc
On Thu, Jan 26, 2017 at 05:45:18PM +0100, Jakub Jelinek wrote:
> On Thu, Jan 26, 2017 at 05:43:13PM +0100, Dominik Vogt wrote:
> > > If the predicates are supposed to ensure it, then I think the assert is
> > > fine.
> >
> > Is it guaranteed that the predicate conditions are evaluated
> > before e
Hi!
I'd like to ping 3 patches:
PR debug/78835 P1 -fdebug-types-section fix
http://gcc.gnu.org/ml/gcc-patches/2017-01/msg01316.html
PR debug/79129 P1 another -fdebug-types-section fix
http://gcc.gnu.org/ml/gcc-patches/2017-01/msg01478.html
noipa attribute addition
http://gcc.gnu.org/ml/gcc-patc
I merged trunk revision 244947 to the gccgo branch.
Ian
On Wed, Jan 18, 2017 at 11:08 PM, Adam Butcher wrote:
> Hi Jason,
>
> I've reopened 64382 and unhooked it from 61636
> (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64382#c6).
>
> This is a rebase of my original patch for 64382 from April 2015 against latest
> master.
This is OK as a workaround.
We have FAILs in two tests that use { target c++11 } but don't
actually compile in C++11 mode. One because default member
initializers make the type a non-aggregate so it can't be
list-initialized and one because it uses std::less<>.
There are also some tests for container adaptors which should n
I made tr1::conj just a using-declaration for std::conj, forgetting
that the overloads for scalars are not present in C++98. This reverts
the part of the change.
PR libstdc++/70607
* include/tr1/complex (conj): Remove using-declaration and restore
overloads, reverting pr
OK.
On Tue, Jan 24, 2017 at 5:43 PM, Jakub Jelinek wrote:
> Hi!
>
> r215070 moved -Winvalid-offsetof pedwarn from build_class_member_access_expr
> (where it warned even about offsetof-like hand-written constructs) to
> finish_offsetof. That is fine, the problem is that while
> build_class_member
When I updated to Go 1.8, the initsig function moved from
signal1_unix.go to signal_unix.go, and lost a gccgo-specific change in
the move. Add it back.
This would have been caught by the misc/cgo/testcarchive tests in the
gc repository, but we don't run those in the gccgo repository. We
should f
This patch to libgo fixes the context used by the getTraceback
function. I passed the wrong context, and that error was hidden by
the ucontext_arg function. This would have been caught by some of the
runtime package tests, but we don't run most of them because they rely
on `go build`, and the go
On Thu, Jan 26, 2017 at 01:57:02PM +0100, Bernd Schmidt wrote:
> On 01/25/2017 08:46 PM, Segher Boessenkool wrote:
> >
> >It turns out my patch (see the PR) causes (or at least triggers)
> >miscompilations on tilegx. I will drop it for now.
>
> Curious, it looked very reasonable. What's needed to
The begin/end versioned namespace macros are misplaced (or missing) in
and and
, the latter of which introduces new ambiguities in C++17
mode.
This fixes that regression, and removes some unnecessary __identity
helpers, as we can just use std::common_type instead (which is
equivalent to decay f
On 01/25/2017 11:09 PM, Marc Glisse wrote:
I assume this causes a regression for code like
unsigned f(unsigned a){
unsigned b=a+1;
if(bSo, it's not terrible to catch this in a manner similar to how we find
other ADD_OVERFLOW cases. And the positive is that we obviously pick it
up for cas
It turns out that because the compiler uses a hash table to save the
cl_target_option structures it is unsafe to modify the result of
build_target_option_node() (doing so will cause the hash lookup to
fail). This PR was due to not properly understanding this limitation.
The fix is to create tempo
Hi Jakub,
On Thu, Jan 26, 2017 at 02:29:51PM +0100, Jakub Jelinek wrote:
> Hi!
>
> I've noticed that the file &1 in libgomp/testsuite/ directory after make
> check and left over hsa_offloading_src*.exe files.
> After looking more carefully, I found various issues.
> 1) the way check_compile is in
On Wed, 25 Jan 2017, Martin Liška wrote:
> Following patch adds what was said in the changes file to our
> documentation.
+constructors with priority support, the profiling properly handles
constructors,
+destructors and C++ constructors (and destructors) of classes which are used
Just "profili
Hi Martin,
On Wed, 25 Jan 2017, Martin Liška wrote:
> Following patch documents DO loop changes which were done for upcoming
> GCC 7.1.
thanks for putting this together.
Index: htdocs/gcc-7/changes.html
===
+
+DO loops with s
The following patch fixes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79131
The patch also adapts IP IRA in LRA because without it GCC IP RA tests
become broken (it was just a luck that the tests worked before the patch).
The patch was successfully bootstrapped and tested on x86-64.
Committ
On Thu, Jan 26, 2017 at 05:43:13PM +0100, Dominik Vogt wrote:
> > If the predicates are supposed to ensure it, then I think the assert is
> > fine.
>
> Is it guaranteed that the predicate conditions are evaluated
> before executing the conditions?
Yes. You can see it in insn-recog.c...
On Thu, Jan 26, 2017 at 05:33:18PM +0100, Jakub Jelinek wrote:
> On Thu, Jan 26, 2017 at 05:11:27PM +0100, Dominik Vogt wrote:
> > The patch fixes the s390x crash reported in PR 79240:
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79240
> > Regression tested and bootstrapped on s390x biarch and
On Thu, Jan 26, 2017 at 05:11:27PM +0100, Dominik Vogt wrote:
> The patch fixes the s390x crash reported in PR 79240:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79240
> Regression tested and bootstrapped on s390x biarch and s390.
> gcc/ChangeLog-pr79240
>
> PR target/79240
> * con
The "internals" documentation has a "Testsuites" chapter; this patch
adds some notes to it, describing the __GIMPLE and __RTL extensions
to the C frontend.
Builds; passed visual inspection of .info, .html, .pdf. and .dvi.
OK for trunk?
gcc/ChangeLog:
* doc/sourcebuild.texi (Testsuites):
I'm receiving the following error message for the new testcase:
FAIL: c-c++-common/Wduplicated-branches-13.c -std=gnu++98 (test for
excess errors)
Excess errors:
/nasfarm/edelsohn/src/src/gcc/testsuite/c-c++-common/Wduplicated-branches-13.c:11:7:
warning: this decimal constant is unsigned only in
The patch fixes the s390x crash reported in PR 79240:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79240
Regression tested and bootstrapped on s390x biarch and s390.
Ciao
Dominik ^_^ ^_^
--
Dominik Vogt
IBM Germany
gcc/ChangeLog-pr79240
PR target/79240
* config/s390/s390.c (s
The attached patch reactivates the setmem_long_and* patterns on
S/390 that have not been generated for a while. Regression tested
and bootstrapped on s390x biarch and s390.
Ciao
Dominik ^_^ ^_^
--
Dominik Vogt
IBM Germany
gcc/ChangeLog-setmem_long_and
* config/s390/s390.md ("*setmem
On 01/26/2017 02:38 AM, Richard Biener wrote:
Marc mentions some reasons we have a lot of single_use predicates on condition
simplifications. You may want to evaluate some of the examples (usually
they boil down to RTL if-conversion missed optimizations). Other cases happen
when we can use CC
On 20/01/17 14:08, Ramana Radhakrishnan wrote:
> On Wed, Dec 28, 2016 at 9:58 AM, Andre Vieira (lists)
> wrote:
>> On 29/11/16 09:45, Andre Vieira (lists) wrote:
>>> On 17/11/16 10:00, Ramana Radhakrishnan wrote:
On Thu, Oct 6, 2016 at 2:57 PM, Andre Vieira (lists)
wrote:
> Hello,
>
On 01/25/2017 11:09 PM, Marc Glisse wrote:
On Wed, 25 Jan 2017, Jeff Law wrote:
As has been discussed extensively, we're not doing a good job at
simplifying overflow tests, particularly those which collapse down to
an EQ/NE test.
x + -1 > x -> x == 0
x + -1 < x -> x != 0
x + 1 < x -> x ==
vague_linkage_p has been assuming that anything with !TREE_PUBLIC is
internal, and so does not have vague linkage. That isn't true for
decloned constructors: the decloned variant which is called by the
complete and base variants is !TREE_PUBLIC because it's local to the
comdat group, but it still
Attribute "strong" on a using-directive was a G++ extension that
eventually became C++11 inline namespaces. It's been documented as
deprecated for a while, but we didn't actually warn about it. This
patch adds such a warning and removes the documentation.
Tested x86_64-pc-linux-gnu, applying to
On 24.01.2017 19:30, Pekka Jääskeläinen wrote:
> Hi,
>
> On Tue, Jan 24, 2017 at 7:26 PM, Joseph Myers wrote:
>> Since front ends can't be enabled or disabled on a per-multilib basis, if
>> you want to support any x86/x86_64 GNU/Linux configuration you need to
>> support all of them here (and pos
On Thu, Jan 26, 2017 at 02:59:50PM +0100, Martin Liška wrote:
> On 01/26/2017 02:19 PM, Jakub Jelinek wrote:
> > On Thu, Jan 26, 2017 at 02:04:00PM +0100, Martin Liška wrote:
> >> + The option is enabled with -fsanitize=address and disabled
> >
> > s/enabled/& by default/
> > s/disabled/& by defa
On 01/26/2017 02:19 PM, Jakub Jelinek wrote:
> On Thu, Jan 26, 2017 at 02:04:00PM +0100, Martin Liška wrote:
>> + The option is enabled with -fsanitize=address and disabled
>
> s/enabled/& by default/
> s/disabled/& by default/
>
>> + with -fsanitize=kernel-address.
>> + Compared to the LLVM c
Hi!
I've noticed that the file &1 in libgomp/testsuite/ directory after make
check and left over hsa_offloading_src*.exe files.
After looking more carefully, I found various issues.
1) the way check_compile is invoked leaves result with values on which
lindex doesn't do what is expected to do
2) "
On Thu, Jan 26, 2017 at 04:48:07AM -0800, Kirill Yukhin wrote:
> Hello,
> Two tests are failing for me on 32b variant bacause of wrong constants.
> Fixed. Tests now pass (under SDE).
>
> gcc/testsuite/
> * gcc.target/i386/avx512bw-kshiftlq-2.c: Use unsigned long long
> constant.
>
On Thu, Jan 26, 2017 at 02:04:00PM +0100, Martin Liška wrote:
> + The option is enabled with -fsanitize=address and disabled
s/enabled/& by default/
s/disabled/& by default/
> + with -fsanitize=kernel-address.
> + Compared to the LLVM compiler, where the option already exists,
> + the impleme
Hi JonY,
On 19/01/17 01:37, JonY wrote:
On 01/18/2017 09:48 AM, Thomas Preudhomme wrote:
By default, wildcard support on Windows for programs compiled with mingw
depends on how the mingw runtime was configured. This means if one wants
to build GCC for Windows with a consistent behavior with Wil
On 01/25/2017 04:06 PM, Jakub Jelinek wrote:
> On Wed, Jan 25, 2017 at 03:00:19PM +, Kyrill Tkachov wrote:
>> Hi Martin,
>>
>> On 25/01/17 14:54, Martin Liška wrote:
>>> Hello.
>>>
>>> Following patch documents new option -fsanitize-address-use-after-scope
>>> which was done for upcoming GCC 7
On 01/25/2017 08:46 PM, Segher Boessenkool wrote:
It turns out my patch (see the PR) causes (or at least triggers)
miscompilations on tilegx. I will drop it for now.
Curious, it looked very reasonable. What's needed to reproduce this?
Bernd
Hello,
Two tests are failing for me on 32b variant bacause of wrong constants.
Fixed. Tests now pass (under SDE).
gcc/testsuite/
* gcc.target/i386/avx512bw-kshiftlq-2.c: Use unsigned long long
constant.
* gcc.target/i386/avx512bw-kshiftrq-2.c: Ditto.
If no objections from
On Thu, Jan 26, 2017 at 1:04 PM, Aldy Hernandez wrote:
> On 01/24/2017 07:23 AM, Richard Biener wrote:
>>
>> On Mon, Jan 23, 2017 at 6:26 PM, Aldy Hernandez wrote:
>>>
>>> On 01/18/2017 10:10 AM, Richard Biener wrote:
On Fri, Jan 13, 2017 at 7:48 PM, Aldy Hernandez
wrote:
>>>
On Thu, Jan 26, 2017 at 1:20 PM, Jakub Jelinek wrote:
> On Thu, Jan 26, 2017 at 01:17:03PM +0100, Richard Biener wrote:
>> On Thu, Jan 26, 2017 at 12:21 PM, Marek Polacek wrote:
>> > This testcase was breaking because we found ourselves in operand_equal_p
>> > with a COND_EXPR whose operand 2 was
On 26 Jan 13:05, Jakub Jelinek wrote:
> On Thu, Jan 26, 2017 at 03:53:44AM -0800, Kirill Yukhin wrote:
> > Hi,
> > On 26 Jan 12:49, Thomas Schwinge wrote:
> > > Hi!
> > >
> > > On Thu, 26 Jan 2017 02:44:56 -0800, Kirill Yukhin
> > > wrote:
> > > > On 26 Jan 10:14, Thomas Schwinge wrote:
> > > > >
On Thu, Jan 26, 2017 at 01:17:03PM +0100, Richard Biener wrote:
> On Thu, Jan 26, 2017 at 12:21 PM, Marek Polacek wrote:
> > This testcase was breaking because we found ourselves in operand_equal_p
> > with a COND_EXPR whose operand 2 was null -- i.e., missing else branch,
> > which won't happen f
On Thu, Jan 26, 2017 at 12:21 PM, Marek Polacek wrote:
> This testcase was breaking because we found ourselves in operand_equal_p
> with a COND_EXPR whose operand 2 was null -- i.e., missing else branch,
> which won't happen for ? : but can happen here via -Wduplicated-branches.
>
> Bootstrapped/r
On Thu, Jan 26, 2017 at 03:53:44AM -0800, Kirill Yukhin wrote:
> Hi,
> On 26 Jan 12:49, Thomas Schwinge wrote:
> > Hi!
> >
> > On Thu, 26 Jan 2017 02:44:56 -0800, Kirill Yukhin
> > wrote:
> > > On 26 Jan 10:14, Thomas Schwinge wrote:
> > > > I see:
> > > >
> > > > {+FAIL: gcc.target/i386/avx5
On 01/24/2017 07:23 AM, Richard Biener wrote:
On Mon, Jan 23, 2017 at 6:26 PM, Aldy Hernandez wrote:
On 01/18/2017 10:10 AM, Richard Biener wrote:
On Fri, Jan 13, 2017 at 7:48 PM, Aldy Hernandez wrote:
Hi Richard.
I'd be happy to provide a patch, but could you please elaborate, as I'm
af
Hi!
On Thu, Jan 26, 2017 at 01:30:21PM +0200, Pekka Jääskeläinen wrote:
> diff --git a/ChangeLog b/ChangeLog
> index 9695f9d..6f4f256 100644
> --- a/ChangeLog
> +++ b/ChangeLog
> @@ -1,3 +1,9 @@
> +2017-01-26 Pekka Jskel??inen
> +
> + * configure.ac: Added i[3456789]86-*-linux* as a sup
Hi,
On 26 Jan 12:49, Thomas Schwinge wrote:
> Hi!
>
> On Thu, 26 Jan 2017 02:44:56 -0800, Kirill Yukhin
> wrote:
> > On 26 Jan 10:14, Thomas Schwinge wrote:
> > > I see:
> > >
> > > {+FAIL: gcc.target/i386/avx512f-ktestw-2.c (test for excess errors)+}
> > > {+UNRESOLVED: gcc.target/i386/a
Hi!
On Thu, 26 Jan 2017 02:44:56 -0800, Kirill Yukhin
wrote:
> On 26 Jan 10:14, Thomas Schwinge wrote:
> > I see:
> >
> > {+FAIL: gcc.target/i386/avx512f-ktestw-2.c (test for excess errors)+}
> > {+UNRESOLVED: gcc.target/i386/avx512f-ktestw-2.c compilation failed to
> > produce executab
On 26/01/17 01:05 +0100, Jakub Jelinek wrote:
On Tue, Jan 24, 2017 at 06:33:51PM +, Jonathan Wakely wrote:
--- a/libstdc++-v3/libsupc++/new_opa.cc
+++ b/libstdc++-v3/libsupc++/new_opa.cc
@@ -55,9 +55,30 @@ extern "C" void *memalign(std::size_t boundary, std::size_t
size);
#endif
#define a
Hi,
Here's a patch which I believe should address all the pointed out BRIG
FE related issues that
have not been committed yet.
I didn't introduce new fixed width int type nodes to tree.h as that
felt too intrusive at this point.
Also, changes.html is still to add.
OK for trunk?
BR,
Pekka
On
On Thu, Jan 26, 2017 at 12:21:02PM +0100, Marek Polacek wrote:
> This testcase was breaking because we found ourselves in operand_equal_p
> with a COND_EXPR whose operand 2 was null -- i.e., missing else branch,
> which won't happen for ? : but can happen here via -Wduplicated-branches.
>
> Bootst
Hi!
I've noticed this test leaves behind declare_simd_2_mod.mod
file. The standard module search can't figure it out because
include is used, thus it has to be specified manually.
Fixed thusly, regtested on x86_64-linux, committed to trunk.
2017-01-26 Jakub Jelinek
* testsuite/libgo
This testcase was breaking because we found ourselves in operand_equal_p
with a COND_EXPR whose operand 2 was null -- i.e., missing else branch,
which won't happen for ? : but can happen here via -Wduplicated-branches.
Bootstrapped/regtested on x86_64-linux, ok for trunk?
2017-01-26 Marek Polace
Hi!
If configured --enable-offload-targets=nvptx-none but for whatever
reason we can't offload to PTX (missing libgomp-nvptx* plugin,
missing libcuda.so.1, missing NVidia HW), lots of libgomp tests
fail. The problem is that if there is simd combined with some
other loop (e.g. distribute simd, for
On Thu, Jan 26, 2017 at 12:00 PM, Jakub Jelinek wrote:
> On Thu, Jan 26, 2017 at 11:54:52AM +0100, Uros Bizjak wrote:
>> On Thu, Jan 26, 2017 at 11:51 AM, Jakub Jelinek wrote:
>> > On Thu, Jan 26, 2017 at 02:44:56AM -0800, Kirill Yukhin wrote:
>> >> Hello Thomas,
>> >> On 26 Jan 10:14, Thomas Sch
On Thu, Jan 26, 2017 at 11:54:52AM +0100, Uros Bizjak wrote:
> On Thu, Jan 26, 2017 at 11:51 AM, Jakub Jelinek wrote:
> > On Thu, Jan 26, 2017 at 02:44:56AM -0800, Kirill Yukhin wrote:
> >> Hello Thomas,
> >> On 26 Jan 10:14, Thomas Schwinge wrote:
> >> > I see:
> >> >
> >> > {+FAIL: gcc.targe
On Thu, Jan 26, 2017 at 11:51 AM, Jakub Jelinek wrote:
> On Thu, Jan 26, 2017 at 02:44:56AM -0800, Kirill Yukhin wrote:
>> Hello Thomas,
>> On 26 Jan 10:14, Thomas Schwinge wrote:
>> > I see:
>> >
>> > {+FAIL: gcc.target/i386/avx512f-ktestw-2.c (test for excess errors)+}
>> > {+UNRESOLVED:
> On Tue, Jan 24, 2017 at 05:27:26PM +, David Sherwood wrote:
> > I have a patch to fix the following openmp issue:
> >
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79212
> >
> > Writing openmp directives in a certain way in fortran programs can
> > lead to the following assert:
> >
> > int
On Thu, Jan 26, 2017 at 09:57:14AM +0100, Thomas Schwinge wrote:
> Hi!
>
> On Mon, 23 Jan 2017 10:19:33 +0100, Martin Liška wrote:
> > --- a/gcc/testsuite/gcc.dg/asan/use-after-scope-3.c
> > +++ b/gcc/testsuite/gcc.dg/asan/use-after-scope-3.c
> > @@ -1,5 +1,6 @@
> > // { dg-do run }
> > // { dg
On Thu, Jan 26, 2017 at 02:44:56AM -0800, Kirill Yukhin wrote:
> Hello Thomas,
> On 26 Jan 10:14, Thomas Schwinge wrote:
> > I see:
> >
> > {+FAIL: gcc.target/i386/avx512f-ktestw-2.c (test for excess errors)+}
> > {+UNRESOLVED: gcc.target/i386/avx512f-ktestw-2.c compilation failed to
> > p
Hello Thomas,
On 26 Jan 10:14, Thomas Schwinge wrote:
> I see:
>
> {+FAIL: gcc.target/i386/avx512f-ktestw-2.c (test for excess errors)+}
> {+UNRESOLVED: gcc.target/i386/avx512f-ktestw-2.c compilation failed to
> produce executable+}
>
> ... because of:
>
> /tmp/ccjv3mX2.s: Assembler me
> On Thu, Jan 26, 2017 at 11:04 AM, Jan Hubicka wrote:
> >> > + if (!contains_hot_bb && speed_p)
> >> > + contains_hot_bb |= optimize_bb_for_speed_p (bb);
> >> > +
> >>
> >> Hmm, but you are also counting the destination of the threading here
> >> which we will
> >> not duplicate. Shou
On Thu, Jan 26, 2017 at 11:04 AM, Jan Hubicka wrote:
>> > + if (!contains_hot_bb && speed_p)
>> > + contains_hot_bb |= optimize_bb_for_speed_p (bb);
>> > +
>>
>> Hmm, but you are also counting the destination of the threading here
>> which we will
>> not duplicate. Shouldn't this be un
> > + if (!contains_hot_bb && speed_p)
> > + contains_hot_bb |= optimize_bb_for_speed_p (bb);
> > +
>
> Hmm, but you are also counting the destination of the threading here
> which we will
> not duplicate. Shouldn't this be under the if (j < path_length - 1)
> conditional so we
> look
On Thu, Jan 26, 2017 at 10:14 AM, Thomas Schwinge
wrote:
> Hi!
>
> On Fri, 20 Jan 2017 23:03:53 +0300, Andrew Senkevich
> wrote:
>> diff --git a/gcc/testsuite/gcc.target/i386/avx512f-ktestw-2.c
>> b/gcc/testsuite/gcc.target/i386/avx512f-ktestw-2.c
>> new file mode 100644
>> index 000..6602c
On Thu, Jan 26, 2017 at 1:06 AM, Jeff Law wrote:
> As has been discussed extensively, we're not doing a good job at simplifying
> overflow tests, particularly those which collapse down to an EQ/NE test.
>
> x + -1 > x -> x == 0
> x + -1 < x -> x != 0
> x + 1 < x -> x == -1U
> x + 1 > x -> x
Hi!
On Fri, 20 Jan 2017 23:03:53 +0300, Andrew Senkevich
wrote:
> diff --git a/gcc/testsuite/gcc.target/i386/avx512f-ktestw-2.c
> b/gcc/testsuite/gcc.target/i386/avx512f-ktestw-2.c
> new file mode 100644
> index 000..6602c7a
> --- /dev/null
> +++ b/gcc/testsuite/gcc.target/i386/avx512f-ktes
On Wed, Jan 25, 2017 at 7:11 PM, Jan Hubicka wrote:
> Hi,
> this patch modifies profitable_jump_thread_path heuristics by enabling
> code expansion when the threaded path contains at least one hot path.
> The basic idea is that while we do not decrease instruction count on the
> non-duplicated pat
1 - 100 of 103 matches
Mail list logo