Hi,
Thanks for the review and suggestions.
> I think the patch isn't quite complete yet. You will also need changes in
> generic code. Currently sched_macro_fuse_insns() does:
Modified the sched_macro_fuse_insns() as required.
> Basically the idea is to push the check for CC usage into target
Hi,
Please find attached the patch that moves the check for CC usage in
any_condjump_p from sched-deps to target macros.
Currently the check is used only by i386 and AArch64.
The general condition checks for the fusion candidates to use/modify CC1
register. However, the fusion of ALU and Branch
On Sun, Mar 26, 2017 at 06:45:07PM -0700, Jerry DeLisle wrote:
> On 03/26/2017 11:45 AM, Steve Kargl wrote:
> > On Sun, Mar 26, 2017 at 11:27:59AM -0700, Jerry DeLisle wrote:
> >>
> >> +#pragma GCC diagnostic push
> >> +#pragma GCC diagnostic ignored "-Wimplicit-fallthrough"
> >
> > IMNSHO, the
On 03/26/2017 11:45 AM, Steve Kargl wrote:
> On Sun, Mar 26, 2017 at 11:27:59AM -0700, Jerry DeLisle wrote:
>>
>> +#pragma GCC diagnostic push
>> +#pragma GCC diagnostic ignored "-Wimplicit-fallthrough"
>
> IMNSHO, the correct fix is to complain loudly to whomever
> added -Wimplicit-fallthrough
Nitish works for IBM and I can stand in as the contributor. The patch
would be very helpful to work around an AIX exception handling
problem.
Because the patch is a generic option and not target-specific, it
needs a build machinery maintainer or Global Reviewer to approve.
Thanks, David
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38822
--- Comment #21 from kargl at gcc dot gnu.org ---
(In reply to Dominique d'Humieres from comment #19)
> > AFAICS everthing is fixed here. Can we close this PR?
>
> Without objection I'll proceed.
Should the bug be fixed before proceeding? See
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38822
kargl at gcc dot gnu.org changed:
What|Removed |Added
CC||kargl at gcc dot gnu.org
---
Hello,
> I got some review comment from Bernhard Reutner-Fischer, and I have
> updated the patch accordingly.
> This patch is for bug opened
> here:https://sourceware.org/bugzilla/show_bug.cgi?id=21187
This patch has been identified as one of the desirable patches
to have for the GDB 8.0
On 03/25/2017 12:26 AM, Marshall Lee Whittaker wrote:
Hi,
I was looking through the historic archives of gcc at ftp.vim.org and
found a very old version of gcc dating back to 1987. I was wondering if
the below thread still applies?
As in, does anybody happen to have any very old original
Snapshot gcc-7-20170326 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/7-20170326/
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80199
Martin Sebor changed:
What|Removed |Added
Keywords||diagnostic
Hi Dominique,
A long time ago Paul sent me the following patch that fixes
all three submodule ICEs in pr69498
Got any more patches like that? If so, could you maybe attach
them to the relevant PRs? Even if such patches should turn out not to
be perfect, they could still help.
Regarding the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80191
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
--- Comment #3
Hi!
On Sat, Mar 25, 2017 at 07:45:53AM +0100, Jakub Jelinek wrote:
> On Fri, Mar 24, 2017 at 06:37:46PM -0500, Segher Boessenkool wrote:
> > On Fri, Mar 24, 2017 at 08:36:16PM +0100, Jakub Jelinek wrote:
> > > + /* Skip over reg notes not related to CFI information. */
> > > + while (n1)
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80204
Bug ID: 80204
Summary: macosx-version-min wrong for macOS Sierra 10.12.3
Product: gcc
Version: 7.0.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
On 03/26/2017 02:13 PM, Gerald Pfeifer wrote:
Hi Jonathan,
On Tue, 23 Feb 2016, Jonathan Wakely wrote:
On 19/02/16 13:17 -0700, Sandra Loosemore wrote:
I suppose the patch is OK as it stands, but I was going to suggest
restructuring it so that it talks about the default behavior first
and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78670
Jerry DeLisle changed:
What|Removed |Added
CC||janus at gcc dot gnu.org
Hi Jonathan,
On Tue, 23 Feb 2016, Jonathan Wakely wrote:
On 19/02/16 13:17 -0700, Sandra Loosemore wrote:
I suppose the patch is OK as it stands, but I was going to suggest
restructuring it so that it talks about the default behavior first and what
it does with non-default -std= options after
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80203
Bug ID: 80203
Summary: libiberty fails to compile regex.c correctly when gcc
is configured --with-sysroot
Product: gcc
Version: unknown
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79434
Paul Thomas changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79434
--- Comment #5 from Paul Thomas ---
Author: pault
Date: Sun Mar 26 20:01:07 2017
New Revision: 246486
URL: https://gcc.gnu.org/viewcvs?rev=246486=gcc=rev
Log:
2017-03-26 Paul Thomas
PR fortran/79434
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80189
--- Comment #3 from Roland Illig ---
To me that would be fine since then I had not even looked at what the %qs might
be. But like the code is now, I suspected the %s to be part of the grammar of
the diagnostic.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80183
--- Comment #7 from François Dumont ---
(In reply to Jonathan Wakely from comment #4)
> I think this is my fault, I asked François to remove a store to _M_color
> that I thought was redundant.
I was surprised that _M_color wasn't move along
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80202
Bug ID: 80202
Summary: Spurious warning "array subscript is below array
bounds" with if-statement and char to unsigned int
conversion
Product: gcc
Version: 6.3.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80201
Bug ID: 80201
Summary: groff build fails with -floop-nest-optimize
-fgraphite-identity
Product: gcc
Version: 6.3.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80196
Roman changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80200
Bug ID: 80200
Summary: decNumber.c : error : #include_next is a GCC extension
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65917
Julian Taylor changed:
What|Removed |Added
CC||jtaylor.debian at googlemail
dot c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80198
--- Comment #3 from Andrew Pinski ---
r233207
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80198
Julian Taylor changed:
What|Removed |Added
Summary|regression, does not|regression [6/7], does not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79434
--- Comment #4 from paul.richard.thomas at gmail dot com ---
Hi Dominiq,
As soon as I have a minute or two, I will back port it. My business is
taking me 7/7 at the moment.
Thanks for the reminder.
Paul
On 26 March 2017 at 17:36, dominiq at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80184
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80199
Bug ID: 80199
Summary: Wlogical-op inconsistent from int to float ?
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79434
Dominique d'Humieres changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #3 from
On Sunday 26 March 2017, Egor Pugin wrote:
> Hi,
>
> It's a bit early question, but still.
> C++ releases became more predictive and regular.
> What do you think about settings -std=c++17 (or gnu++17) for gcc-8 as
> default c++ mode?
> What is your policy regarding default c++ standards in gcc?
The attached patch fixes the alias requirement for gcc.dg/torture/pr79732.c and
gcc.dg/tree-ssa/pr56727.c,
so the tests don't fail on 32-bit hppa-hpux. Committed to trunk.
Dave
--
John David Anglin dave.ang...@bell.net
2017-03-26 John David Anglin
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80198
Julian Taylor changed:
What|Removed |Added
Summary|does not vectorize generic |regression, does not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53542
--- Comment #2 from Dominique d'Humieres ---
From comment 0, obvious patch
--- ../_clean/gcc/fortran/expr.c2017-03-22 17:29:45.0 +0100
+++ gcc/fortran/expr.c 2017-03-26 16:12:21.0 +0200
@@ -2591,7 +2591,7 @@
This patch fixes some new coarray testsuite fails on hppa. Committed to trunk.
Dave
--
John David Anglin dave.ang...@bell.net
2017-03-26 John David Anglin
* gfortran.dg/coarray_failed_images_1.f08: Add "-latomic" option if
libatomic_available.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80198
Bug ID: 80198
Summary: does not vectorize generic inplace integer operation
Product: gcc
Version: 6.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80187
Tim Shen changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
c,c++,lto,fortran
--enable-lto -enable-libitm -disable-multilib
Thread model: posix
gcc version 7.0.1 20170326 (experimental) [trunk revision 246482] (GCC)
gcc -O2 fullMC.c -g
real0m0.489s
user0m0.485s
sys 0m0.002s
Performance counter stats for './a.out':
486.303424 t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38822
--- Comment #19 from Dominique d'Humieres ---
> AFAICS everthing is fixed here. Can we close this PR?
Without objection I'll proceed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80191
--- Comment #2 from Roland Illig ---
But then shouldn't it be spelled "new-initializer", not "new initializer"?
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the German team of translators. The file is available at:
http://translationproject.org/latest/gcc/de.po
(This file, 'gcc-7.1-b20170226.de.po',
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80196
--- Comment #4 from Roman ---
Thank you for your quick response.
I am using Gentoo. I'll give that option a try.
The build system is:
/usr/local/bin/gcc --version
gcc (GCC) 7.0.1 20170304 (experimental)
Copyright (C) 2017 Free Software
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80183
Markus Trippelsdorf changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80196
--- Comment #3 from Jonathan Wakely ---
Maybe PR 40974 again, which nobody can reproduce as it only happens due to some
system-specific weirdness. We need more information about your system, what
kind of OS distro are you using? etc. etc.
Could
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80183
--- Comment #5 from Markus Trippelsdorf ---
Author: trippels
Date: Sun Mar 26 12:33:35 2017
New Revision: 246483
URL: https://gcc.gnu.org/viewcvs?rev=246483=gcc=rev
Log:
Fix PR80183 : _M_color not moved
PR libstdc++/80183
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80191
Jonathan Wakely changed:
What|Removed |Added
CC||jason at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80183
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #4 from Jonathan
On 26/03/17 11:54 +0200, Markus Trippelsdorf wrote:
clang-format stopped working when compiled with gcc-7.
It turned out that an uninitialized _M_color is responsible.
The fix is easy, just copy _M_color in the move case, too.
Tested on ppc64le.
OK for trunk?
OK, thanks.
A reduced testcase
Dear Nicolas,
A long time ago Paul sent me the following patch that fixes all three submodule
ICEs in pr69498
Index: gcc/fortran/module.c
===
*** gcc/fortran/module.c(revision 236994)
--- gcc/fortran/module.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80196
--- Comment #2 from Roman ---
Revision 246482.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80196
--- Comment #1 from Roman ---
I configured the build as follows:
/home/roman/gcc-source/configure
Best regards,
Roman
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80196
Bug ID: 80196
Summary: fenv_t not declared
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80189
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #2
Hi,
It's a bit early question, but still.
C++ releases became more predictive and regular.
What do you think about settings -std=c++17 (or gnu++17) for gcc-8 as
default c++ mode?
What is your policy regarding default c++ standards in gcc?
--
Egor Pugin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80195
Bug ID: 80195
Summary: Message build from untranslated string concatenation
in fortran/resolve.c:14529
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity:
clang-format stopped working when compiled with gcc-7.
It turned out that an uninitialized _M_color is responsible.
The fix is easy, just copy _M_color in the move case, too.
Tested on ppc64le.
OK for trunk?
Thanks.
PR libstdc++/80183
* include/bits/stl_tree.h:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80183
Markus Trippelsdorf changed:
What|Removed |Added
Target Milestone|--- |7.0
--- Comment #3 from Markus
61 matches
Mail list logo