Snapshot gcc-7-20160925 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/7-20160925/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 7 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision
> There is no hurry to kill old reload. As you say, many targets will
> not be converted soon. But one day it will be removed. Not in GCC 7,
> not in GCC 8 almost certainly. But one day.
Certainly not in GCC 8, the top priority is IMO the cc0 thing and you cannot
really do both at the same
Hi,
Here's a report of a successful build and install of GCC:
$ gcc-6.2.0/config.guess
powerpc64-unknown-linux-gnu
$ newcompiler/bin/gcc -v
Using built-in specs.
COLLECT_GCC=newcompiler/bin/gcc
Hi Martin,
in the past I have seen (and fixed) code like
sprintf(buf, "%s %d", buf, x);
that may possibly work by chance, but usually
produces undefined results.
Do you see a way to enhance the warning for cases
where the output buffer overlaps an input buffer?
Thanks
Bernd.
On Sun, Sep 25, 2016 at 10:46:55AM +0200, Eric Botcazou wrote:
> > There is no hurry to kill old reload. As you say, many targets will
> > not be converted soon. But one day it will be removed. Not in GCC 7,
> > not in GCC 8 almost certainly. But one day.
>
> Certainly not in GCC 8, the top
On Sun, Sep 25, 2016 at 04:28:04PM +0900, Oleg Endo wrote:
> > > ANd yes, I see this as a way to deprecating those cc0 targets like
> > > the
> > > m68k :-)
> > Would be a shame to see m68k go. There still is time...
>
> Indeed. 68K is a perfect candidate for addressing mode optimization
>
On 9/25/16, Bernd Edlinger wrote:
> Hi Martin,
>
> in the past I have seen (and fixed) code like
>
> sprintf(buf, "%s %d", buf, x);
>
> that may possibly work by chance, but usually
> produces undefined results.
>
> Do you see a way to enhance the warning for cases
>
> On Sep 25, 2016, at 4:46 AM, Eric Botcazou wrote:
>
>> There is no hurry to kill old reload. As you say, many targets will
>> not be converted soon. But one day it will be removed. Not in GCC 7,
>> not in GCC 8 almost certainly. But one day.
>
> Certainly not in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77738
Bug ID: 77738
Summary: Invalid initialisation of ar.lc register
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
Priority:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68733
--- Comment #10 from John David Anglin ---
Similar fails:
FAIL: c-c++-common/gomp/clauses-2.c (test for errors, line 51)
FAIL: c-c++-common/gomp/clauses-2.c (test for excess errors)
FAIL: c-c++-common/gomp/clauses-2.c -std=c++98 (test for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77735
Bug ID: 77735
Summary: FAIL: gcc.dg/tree-ssa/builtin-sprintf-warn-1.c (test
for warnings, line 358)
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity:
Hi,
May I ask if there is any decision?
Regards,
Yuan, Pengfei
> > > I also like a new param better as it avoids a new magic constant and
> > > makes playing with
> > > it easier (your patch removes the ability to do statistics like you did
> > > via the
> > > early-inlining-insns parameter by
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77593
--- Comment #10 from n8tm at aol dot com ---
Jerry ,
Thanks for the efforts and apparent progress. I will return to wired internet
territory and the win10 box next weekend. I have the win8.1 laptop here.
Sent via the ASUS PadFone X mini, an AT
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77733
Bug ID: 77733
Summary: Add fixit hint suggesting to use std::move
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Keywords: diagnostic
Severity: normal
Priority:
Tested on Linux-x64.
2016-09-26 Ville Voutilainen
PR libstdc++/77727
* include/std/optional (optional(const optional<_Up>&)):
Default-initialize the base and use emplace.
(optional(optional<_Up>&&)): Likewise.
*
On 25/09/16 04:50, kugan wrote:
Hi,
In make_new_ssa_for_def (tree-reassoc.c) we should use gimple_get_lhs to
get lhs instead of gimple_assign_lhs as stmt can be builtins too.
Attached patch fixes this.
Testcase from PR (attached) seems to fail. I dont any fortran so I didnt
try fixing it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77727
Ville Voutilainen changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77727
--- Comment #2 from Ville Voutilainen ---
Patch available: https://gcc.gnu.org/ml/gcc-patches/2016-09/msg01777.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71509
--- Comment #4 from Anton Blanchard ---
Created attachment 39683
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39683=edit
Another bitop LHS test case
Here's another issue found in the Linux kernel. Seems like this should be a
single
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77731
Bug ID: 77731
Summary: Parameter pack expansion doesn't work when used to
define argument list
Product: gcc
Version: 6.2.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77593
--- Comment #9 from Jerry DeLisle ---
(In reply to tprince from comment #8)
> I show my configure parameters in my test results posts. At some time in
> the past, each of them has been important. I don't know if the parameters
> quoted by
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77730
--- Comment #5 from PeteVine ---
OK, I hacked the last two to use -mcpu=cortex-a53 (the first one got switched
to -mtune) and the result looks like this:
http://openbenchmarking.org/result/1609258-LO-FORTRANAA63
Not exactly the original issues
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77736
Bug ID: 77736
Summary: FAIL: gcc.dg/tree-ssa/builtin-sprintf-warn-2.c (test
for warnings, line 50)
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity:
On 09/25/2016 09:10 PM, Arnaud Charlet wrote:
Is the above change really necessary? Would be nice to get rid of this
extra code. The rest looks OK to me.
It is required for support of environment when LFN support is either
not available or disabled for some reason (for example FreeDOS
without
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77737
Bug ID: 77737
Summary: FAIL: gcc.dg/tree-ssa/scev-5.c scan-tree-dump-times
optimized "" 1
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77732
Bug ID: 77732
Summary: FAIL: gcc.dg/ipa/ipcp-cstagg-7.c scan-ipa-dump-times
cp "Discovered an indirect call to a known target" 3
Product: gcc
Version: 7.0
Status:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77733
--- Comment #1 from Jonathan Wakely ---
When template argument deduction is involved and the list of candidates is
displayed, the fixit becomes more useful, as the relevant function can get lost
in the list of failed overload resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77734
Bug ID: 77734
Summary: FAIL: gcc.dg/plugin/must-tail-call-1.c
-fplugin=./must_tail_call_plugin.so (test for excess
errors)
Product: gcc
Version: 7.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77739
Bug ID: 77739
Summary: internal compiler error: in create_tmp_var, at
gimple-expr.c:524
Product: gcc
Version: 5.4.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51244
--- Comment #87 from Oleg Endo ---
Author: olegendo
Date: Sun Sep 25 06:59:37 2016
New Revision: 240471
URL: https://gcc.gnu.org/viewcvs?rev=240471=gcc=rev
Log:
This fixes a fallout that actually goes back to 5.0 but went unnoticed.
The costs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65122
--- Comment #19 from Marc Glisse ---
(In reply to Andrew Pinski from comment #17)
> I think this is fixed for GCC 7 with -std=c++17 support.
No, it isn't. new T[10] will give suitably aligned memory, but not
std::allocator. Only the core part
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58122
--- Comment #5 from Oleg Endo ---
This issue seems to be working just fine. Not sure what kind of test case to
add for this though... just scanning final assembler code for some expected hex
or dec constant?
Hi,
this patch fixes PR77558, an ice-on-invalid-code 6/7 regression.
The fix for PR71602 introduced the invalid-code test-case
c-c++-common/va-arg-va-list-type.c:
...
__builtin_va_list *pap;
void
fn1 (void)
{
__builtin_va_arg (pap, double); /* { dg-error "first argument to
'va_arg' not of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77558
Tom de Vries changed:
What|Removed |Added
Keywords||patch
--- Comment #7 from Tom de Vries
Hi!
Currently CHECKING_P is not a boolean flag but a ternary option.
However the _P in the name implies it is a boolean.
That should be cleaned up again IMHO.
So this patch splits CHECKING_P into CHECKING_P and a new flag
ENABLE_EXTRA_CHECKING. All uses of CHECKING_P are actually of
the form
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77725
Tamir Aviv changed:
What|Removed |Added
CC||tamiraviv at mail dot tau.ac.il
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56365
--- Comment #14 from Oleg Endo ---
Richi, if you're not going to backport any patches, maybe close this one as
fixed?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77719
--- Comment #6 from Joost VandeVondele
---
(In reply to kugan from comment #5)
> Sent a patch to fix this at
> https://gcc.gnu.org/ml/gcc-patches/2016-09/msg01760.html.
Thanks, add this line before the first IF statement to silence the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77714
--- Comment #3 from Bernd Edlinger ---
because a different pattern is choosen for this insn
the reg-note is overwritten here:
Choosing alt 2 in insn 48: (0) l (1) l (2) lL {*thumb1_addsi3}
Creating newreg=129, assigning class
Hi,
This fixes a fallout that actually goes back to 5.0 but went unnoticed.
The costs for movt and movrt type of insns were not correctly reported
and ifcvt thus made some bad choices for SH. A new cset_zero pattern
variant is also required to fix the matching for some recent changes
in the
Hi!
This patch makes -Wint-in-bool-context warn on suspicious integer left
shifts, when the integer is signed, which is most likely some kind of
programming error, for instance using "<<" instead of "<".
The warning is motivated by the fact, that an overflow on integer shift
left is undefined
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71767
--- Comment #24 from Dominique d'Humieres ---
The patch in comment 20 (and SDK 10.9) causes the failures of the tests
gcc.dg/torture/darwin-cfstring-3.c and g++.dg/torture/darwin-cfstring-3.C with
-m32, see
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77729
--- Comment #3 from Julian Andres Klode ---
Created attachment 39677
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39677=edit
arm (thumb2) output at -O2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77729
--- Comment #2 from Julian Andres Klode ---
Created attachment 39676
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39676=edit
Aarch64 output at -O2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77729
--- Comment #1 from Julian Andres Klode ---
Created attachment 39675
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39675=edit
C reproducer
Hi Matthew,
On 27 July 2016 at 15:59, Ramana Radhakrishnan
wrote:
> On Tue, May 17, 2016 at 3:31 PM, Matthew Wahab
> wrote:
>> The ACLE specifies a number of intrinsics for manipulating vectors
>> holding values in most of the integer and
From: Sergei Trofimovich
Today I traced AVX2 optimisation bug in gcc and
distilled it down to '__builtin_ia32_gatheraltdiv4si256'
generated by gcc.
When I attempted to use this builtin directly
in a simple program gcc refused to recognise
it as known:
#include
void a
Tested on Linux-x64.
2016-09-25 Ville Voutilainen
PR libstdc++/77717
* testsuite/21_strings/basic_string_view/operations/compare/char/1.cc:
Fix an out-of-bounds access.
diff --git
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77729
Bug ID: 77729
Summary: aarch64 inserts unneeded uxtb after ldrb, orr ...32
Product: gcc
Version: 6.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77729
Andrew Pinski changed:
What|Removed |Added
CC||pinskia at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77411
--- Comment #4 from Bernd Edlinger ---
Author: edlinger
Date: Sun Sep 25 15:12:05 2016
New Revision: 240472
URL: https://gcc.gnu.org/viewcvs?rev=240472=gcc=rev
Log:
2016-09-25 Bernd Edlinger
backport from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77729
Florian Weimer changed:
What|Removed |Added
CC||fw at gcc dot gnu.org
--- Comment #7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77729
--- Comment #8 from Andrew Pinski ---
This looks like missing removal of casts.
Note in C, char_var|32 is really the same as ((int)char_var)|32
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77730
--- Comment #1 from Andrew Pinski ---
One thing I noticed is the generic vector cost model sucks for almost all
cores. It causes to emit ld2/ld3 in cases where it would be more expensive than
if doing it scalar.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77730
Andrew Pinski changed:
What|Removed |Added
Component|middle-end |target
--- Comment #2 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77729
--- Comment #5 from Julian Andres Klode ---
Created attachment 39678
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39678=edit
ppc64le
Hmm, AFAICT the same seems to happen on powerpc64le:
lbz 9,0(3)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77729
--- Comment #6 from Julian Andres Klode ---
(In reply to Andrew Pinski from comment #4)
> Note this testcase needs to be improved as I have a patch which converts a
> switch with just one case and a default into anew if
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77729
--- Comment #9 from Julian Andres Klode ---
(In reply to Andrew Pinski from comment #8)
> This looks like missing removal of casts.
>
> Note in C, char_var|32 is really the same as ((int)char_var)|32
Well. The loads of the
Hi
Trivial patch to cleanup parallel/algo.h by generalizing usage of
std::__iterator_category.
* include/parallel/algo.h: Generalize usage of
std::__iterator_category.
Adjust whitespaces.
Tested under Linux x86_64 parallel mode.
François
Index: include/parallel/algo.h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77730
Bug ID: 77730
Summary: Fortran performance on aarch64 (6/7 regression
heads-up)
Product: gcc
Version: 6.2.1
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77729
Andrew Pinski changed:
What|Removed |Added
Keywords||missed-optimization
> int
> __gnat_get_maximum_file_name_length (void)
> {
> +#if defined (__DJGPP__)
> + return (_use_lfn(".")) ? -1 : 8;
> +#else
>return -1;
> +#endif
> }
Is the above change really necessary? Would be nice to get rid of this
extra code. The rest looks OK to me.
Arno
On Sun, Sep 25, 2016 at 02:48:19PM +0100, Sergei Trofimovich wrote:
> From: Sergei Trofimovich
>
> Today I traced AVX2 optimisation bug in gcc and
> distilled it down to '__builtin_ia32_gatheraltdiv4si256'
> generated by gcc.
>
> When I attempted to use this builtin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77621
--- Comment #22 from uros at gcc dot gnu.org ---
Author: uros
Date: Sun Sep 25 17:07:37 2016
New Revision: 240475
URL: https://gcc.gnu.org/viewcvs?rev=240475=gcc=rev
Log:
Backport from mainline
2016-09-21 Richard Biener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77621
Uroš Bizjak changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77730
--- Comment #3 from PeteVine ---
What about ARMv7?
http://openbenchmarking.org/result/1609253-LO-MERGE859124
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77730
--- Comment #4 from Andrew Pinski ---
(In reply to PeteVine from comment #3)
> What about ARMv7?
>
> http://openbenchmarking.org/result/1609253-LO-MERGE859124
Similar point there. I have seen cortex-a7 and a9 acting way different.
Also
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71767
--- Comment #25 from Iain Sandoe ---
(In reply to Dominique d'Humieres from comment #24)
> The patch in comment 20 (and SDK 10.9) causes the failures of the tests
> gcc.dg/torture/darwin-cfstring-3.c and g++.dg/torture/darwin-cfstring-3.C
> with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77694
--- Comment #5 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Sun Sep 25 17:30:27 2016
New Revision: 240476
URL: https://gcc.gnu.org/viewcvs?rev=240476=gcc=rev
Log:
2016-09-22 Steven G. Kargl
PR
Committed as "obvious" even though thomas OK patch
in bugzilla audit trail.
2016-09-25 Steven G. Kargl
PR fortran/77694
* frontend-passes.c (optimize_binop_array_assignment): Check pointer
for NULL.
2016-09-25 Steven G. Kargl
On 09/25/2016 07:25 PM, Arnaud Charlet wrote:
int
__gnat_get_maximum_file_name_length (void)
{
+#if defined (__DJGPP__)
+ return (_use_lfn(".")) ? -1 : 8;
+#else
return -1;
+#endif
}
Is the above change really necessary? Would be nice to get rid of this
extra code. The rest looks
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77694
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
> >Is the above change really necessary? Would be nice to get rid of this
> >extra code. The rest looks OK to me.
> It is required for support of environment when LFN support is either
> not available or disabled for some reason (for example FreeDOS
> without LFN support loaded).
Does it matter
On Sun, 25 Sep 2016 19:01:14 +0200
Jakub Jelinek wrote:
> On Sun, Sep 25, 2016 at 02:48:19PM +0100, Sergei Trofimovich wrote:
> > From: Sergei Trofimovich
> >
> > Today I traced AVX2 optimisation bug in gcc and
> > distilled it down to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=76957
--- Comment #4 from John David Anglin ---
Similar fail on hppa-unknown-linux-gnu:
FAIL: gcc.dg/graphite/scop-dsyrk.c scan-tree-dump-times graphite "number of
SCoPs: 1" 1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77429
--- Comment #3 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Sun Sep 25 18:46:28 2016
New Revision: 240477
URL: https://gcc.gnu.org/viewcvs?rev=240477=gcc=rev
Log:
2016-09-25 Steven G. Kargl
PR
Committed as obvious.
2016-09-25 Steven G. Kargl
PR fortran/77429
* dependency.c (gfc_check_dependency): Convert gcc_assert() to
a conditional and possible call to gfc_internal_error().
2016-09-25 Steven G. Kargl
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77429
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
78 matches
Mail list logo