On Mon, Jan 15, 2018 at 01:39:43PM +0100, Sebastian Huber wrote:
> On 13/01/18 00:16, Jeff Law wrote:
> >On 01/12/2018 04:07 PM, Joseph Myers wrote:
> >>On Fri, 12 Jan 2018, Jeff Law wrote:
> >>
> >>>I was going to suggest deprecation for gcc-8 given how badly it was
> >>>broken in gcc-7 and the
On 01/15/2018 05:46 AM, Joseph Myers wrote:
On Mon, 15 Jan 2018, Sebastian Huber wrote:
On 13/01/18 00:16, Jeff Law wrote:
On 01/12/2018 04:07 PM, Joseph Myers wrote:
On Fri, 12 Jan 2018, Jeff Law wrote:
I was going to suggest deprecation for gcc-8 given how badly it was
broken in gcc-7
On Mon, 15 Jan 2018, Martin Sebor wrote:
> I'm having trouble bringing up bugs or updating them. Has
> anyone else noticed Bugzilla (and/or other services running
> on gcc.gnu.org) being very slow or timing out?
I'm presuming this comes from the read errors on sdi that I just reported
to
On Mon, Jan 15, 2018 at 11:28:25AM -0700, Jeff Law wrote:
> > Is cc0 conversion enough to get m68k off the chopping block?
> I would think so for this round. I suspect there'd be another round in
> the future to convert to LRA, but I suspect that'd be *much* smaller.
Yeah. And converting to LRA
On 1/15/2018 11:31 AM, Segher Boessenkool wrote:
On Mon, Jan 15, 2018 at 01:39:43PM +0100, Sebastian Huber wrote:
On 13/01/18 00:16, Jeff Law wrote:
On 01/12/2018 04:07 PM, Joseph Myers wrote:
On Fri, 12 Jan 2018, Jeff Law wrote:
I was going to suggest deprecation for gcc-8 given how
On 01/15/2018 11:11 AM, Joel Sherrill wrote:
>
>
> On 1/15/2018 11:31 AM, Segher Boessenkool wrote:
>> On Mon, Jan 15, 2018 at 01:39:43PM +0100, Sebastian Huber wrote:
>>> On 13/01/18 00:16, Jeff Law wrote:
On 01/12/2018 04:07 PM, Joseph Myers wrote:
> On Fri, 12 Jan 2018, Jeff Law
I'm having trouble bringing up bugs or updating them. Has
anyone else noticed Bugzilla (and/or other services running
on gcc.gnu.org) being very slow or timing out?
Thanks
Martin
Jeff Law writes:
> A change in reload back in 2016 (IIRC) has effectively made m32c
> unusable. The limits of the register file create horrible problems for
> reload.
>
> I was going to suggest deprecation for gcc-8 given how badly it was
> broken in gcc-7 and the lack of
On Mon, Jan 15, 2018 at 10:35 PM, chenzhelu wrote:
> Hello all,
> I encountered a problem on "local class name conflict",
> I searched on net and found that years ago, some people also encoutered this
> kind of problem.
The correct name for this is One Definition Rule (or
On 2018-01-16 14:45, Andrew Pinski wrote:
On Mon, Jan 15, 2018 at 10:35 PM, chenzhelu wrote:
Hello all,
I encountered a problem on "local class name conflict",
I searched on net and found that years ago, some people also encoutered this
kind of problem.
The correct name
Hello all,
I encountered a problem on "local class name conflict",
I searched on net and found that years ago, some people also encoutered this
kind of problem.
https://stackoverflow.com/questions/10671956/same-class-name-in-different-c-files
http://www.cplusplus.com/forum/general/32010/
Hello GCC maintainer,
Our team at Qualcomm Datacenter Technologies, Inc. is interested in
contributing patches to the upstream GCC compiler project. To get the process
started, we'd like to request a copyright assignment form as per contribution
guidelines outlined at
On Mon, Jan 15, 2018 at 12:58 PM, Joseph Myers wrote:
> On Mon, 15 Jan 2018, Martin Sebor wrote:
>
>> I'm having trouble bringing up bugs or updating them. Has
>> anyone else noticed Bugzilla (and/or other services running
>> on gcc.gnu.org) being very slow or timing
On Mon, 15 Jan 2018, Sebastian Huber wrote:
> On 13/01/18 00:16, Jeff Law wrote:
> > On 01/12/2018 04:07 PM, Joseph Myers wrote:
> > > On Fri, 12 Jan 2018, Jeff Law wrote:
> > >
> > > > I was going to suggest deprecation for gcc-8 given how badly it was
> > > > broken in gcc-7 and the lack of
On 13/01/18 00:16, Jeff Law wrote:
On 01/12/2018 04:07 PM, Joseph Myers wrote:
On Fri, 12 Jan 2018, Jeff Law wrote:
I was going to suggest deprecation for gcc-8 given how badly it was
broken in gcc-7 and the lack of maintenance on the target.
While we're considering deprecations, what
Status
==
GCC 8 is in regression and documentation fixes stage now similar as if
trunk was a release branch.
We're still in pretty bad shape regression-wise. Please also take
the opportunity to check the state of your favorite host/target
combination to make sure building and testing works
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83851
Richard Biener changed:
What|Removed |Added
Priority|P3 |P4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83850
--- Comment #5 from Richard Biener ---
Author: rguenth
Date: Mon Jan 15 14:43:52 2018
New Revision: 256700
URL: https://gcc.gnu.org/viewcvs?rev=256700=gcc=rev
Log:
2018-01-15 Richard Biener
PR middle-end/83850
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83859
Bug ID: 83859
Summary: Please add new attribute which will establish relation
between parameters for buffer and its size
Product: gcc
Version: 8.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83862
Bug ID: 83862
Summary: powerpc: ICE in signbit testcase
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83863
Bug ID: 83863
Summary: i386.md:16739:36: warning: logical ‘or’ of
collectively exhaustive tests is always true
[-Wlogical-op]
Product: gcc
Version: 8.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83865
--- Comment #1 from G. Steinmetz ---
A similar pair : ICE with 7/8 for z4.f90, z5.f90 works.
$ cat z4.f90
program p
associate (x => f())
if ( x(1) /= '' ) call abort
end associate
contains
function f()
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83817
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57503
Georg-Johann Lay changed:
What|Removed |Added
Priority|P4 |P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83845
Richard Biener changed:
What|Removed |Added
Priority|P3 |P1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83847
Richard Biener changed:
What|Removed |Added
Target||x86_64-*-*
Priority|P3
In the testcase we were trying to group two gather loads, even though
that isn't supported. Fixed by explicitly disallowing grouping of
gathers and scatters.
This problem didn't show up on SVE because there we convert to
IFN_GATHER_LOAD/IFN_SCATTER_STORE pattern statements, which fail
the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83653
--- Comment #16 from Jakub Jelinek ---
Actually, there is no need to use the __COUNTER__ stuff, just use
static const int __ia64_asr_p = ...;
in the scope. It is just important __OPTIMIZE__ is on, because at -O0 the
compiler wouldn't optimize
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83853
--- Comment #2 from rene.r...@fu-berlin.de ---
Hi,
sorry I submitted accidentally before writing the text.
I am investigating some use cases for condition_variables using c++11 thread
support library.
In my use case I have the following setup.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83816
--- Comment #6 from Oleg Endo ---
I can reproduce it on a different machine. One of the object files in the
whole app build seems to be written bad.
I could isolate the pre-processed .ii file. Compiling that .ii file and trying
to link it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83834
--- Comment #6 from H.J. Lu ---
This may be due to binutils 2.30:
https://sourceware.org/ml/binutils/2018-01/msg00236.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83816
--- Comment #8 from Oleg Endo ---
(In reply to rguent...@suse.de from comment #7)
>
> If you can produce a testcase and attach that that would be nice.
I'm trying. But it's gonna take ages. Have to hand-strip the .ii file line by
line ... or
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83862
Bill Schmidt changed:
What|Removed |Added
Target||powerpc*-*-*
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83861
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83770
Richard Biener changed:
What|Removed |Added
Priority|P3 |P1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83771
Richard Biener changed:
What|Removed |Added
Priority|P3 |P1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83776
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
I was hoping I could ask an ARM backend maintainer to look over the
following patch.
I was examining the code generated for the following C snippet on a
raspberry pi,
static inline int popcount_lut8(unsigned *buf, int n)
{
int cnt=0;
unsigned int i;
do {
i = *buf;
cnt +=
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83858
Bug ID: 83858
Summary: [8 Regression] error: invalid cast from type
'poly_uint16' to type 'long long int'
Product: gcc
Version: 8.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57503
--- Comment #17 from Georg-Johann Lay ---
Obervation that -fno-wrapv also leads to correct code, hence there is somewhere
a wrong assumption that signed overflow occurs (which doesn't).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83858
--- Comment #1 from John David Anglin ---
In varasm.ii, we have
inline __attribute__ ((always_inline)) poly_uint16
GET_MODE_SIZE (machine_mode mode)
{
return mode_to_bytes (mode);
}
template
inline __attribute__ ((always_inline)) typename
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83833
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83864
--- Comment #1 from G. Steinmetz ---
Works outside of a type :
$ cat z2.f90
program p
character :: c(3) = transfer('abc','z',3)
print *, c
end
$ gfortran-8-20180114 z2.f90 -static-libgfortran
$ a.out
abc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83833
--- Comment #2 from Jonathan Wakely ---
Oh, we multiply by two in operator() instead. But is that equivalent?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80870
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |7.3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83806
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |6.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83712
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |6.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82096
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |6.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83816
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |7.3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83808
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |7.3
Add this missing C++17 variable template.
PR libstdc++/83830
* include/std/type_traits (has_unique_object_representations_v): Add
variable template.
* testsuite/20_util/has_unique_object_representations/value.cc: Check
variable template.
Tested
On Mon, Jan 15, 2018 at 1:42 AM, Jakub Jelinek wrote:
> On Sun, Jan 14, 2018 at 06:29:54AM -0800, H.J. Lu wrote:
>> + if (TREE_CODE (field) == FIELD_DECL && DECL_PACKED (field))
>> + {
>> + tree field_type = TREE_TYPE (field);
>> + unsigned int
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83859
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83857
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83837
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83588
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |6.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83796
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |6.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57503
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |6.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83839
H.J. Lu changed:
What|Removed |Added
Attachment #43124|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83860
Bug ID: 83860
Summary: valarray replacement type breaks with auto and more
than one operation
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83858
--- Comment #2 from John David Anglin ---
It looks to me like FUNCTION_ARG_SIZE needs to me to pa.c...
On Mon, Jan 15, 2018 at 3:38 AM, H.J. Lu wrote:
> On Mon, Jan 15, 2018 at 12:31 AM, Richard Biener
> wrote:
>> On Sun, Jan 14, 2018 at 4:08 PM, H.J. Lu wrote:
>>> Now my patch set has been checked into trunk. Here is a patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83620
--- Comment #6 from Vladimir Makarov ---
(In reply to Jakub Jelinek from comment #4)
> Or, alternatively, does --param=max-sched-ready-insns=0 make sense and is it
> supportable? If not, we could just require it to be at least one.
This
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83740
--- Comment #8 from G. Steinmetz ---
I can confirm now that the ICE is gone for all relevant test cases.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83836
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83817
--- Comment #5 from Jakub Jelinek ---
Created attachment 43141
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43141=edit
gcc8-pr83817.patch
Untested fix.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83510
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |8.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83852
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |8.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83793
--- Comment #4 from Matthias Kretz ---
(In reply to Jonathan Wakely from comment #2)
> Looks like a dup of PR 47226
Ah, yes. Sorry for missing it, I recall seeing it before. I agree, a backport
would be nice, but an overhaul is not a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83816
--- Comment #7 from rguenther at suse dot de ---
On January 15, 2018 5:04:14 PM GMT+01:00, "olegendo at gcc dot gnu.org"
wrote:
>https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83816
>
>--- Comment #6 from Oleg Endo ---
ASM_OUTPUT_DEF isn't defined for TARGET_MACHO. Use ASM_OUTPUT_LABEL to
generate the __x86_return_thunk label, instead of the set directive.
Update testcase to remove the __x86_return_thunk label check. Since
-fno-pic is ignored on Darwin, update testcases to sscan or "push"
only on Linux.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83853
Jonathan Wakely changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83825
Richard Biener changed:
What|Removed |Added
Priority|P3 |P4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83817
Richard Biener changed:
What|Removed |Added
Keywords||ice-checking
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57503
Georg-Johann Lay changed:
What|Removed |Added
Component|middle-end |tree-optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83856
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83857
--- Comment #2 from vincenzo Innocente ---
(In reply to Richard Biener from comment #1)
> I've seen a similar bug so maybe fixed already.
if the similar bug is #83753 it is looks "fixed" in the version I tested
(at least
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83830
--- Comment #2 from Jonathan Wakely ---
Author: redi
Date: Mon Jan 15 15:02:01 2018
New Revision: 256701
URL: https://gcc.gnu.org/viewcvs?rev=256701=gcc=rev
Log:
PR libstdc++/83830 Define std::has_unique_object_representations_v
PR
Hi Will,
On Fri, Jan 12, 2018 at 03:22:06PM -0600, Will Schmidt wrote:
> Add support for gimple folding of the mergeh, mergel intrinsics.
> Since the merge low and merge high variants are almost identical, a
> new helper function has been added so that code can be shared.
>
> This also adds
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83330
H.J. Lu changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80276
Jonathan Wakely changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
On Mon, Jan 15, 2018 at 2:50 PM, Peryt, Sebastian
wrote:
> Hi,
>
> This patch re-enables RDRND for Silvermont. It got lost in r206178 as pointed
> out in PR.
> Bootstraped and tested.
>
> 2018-01-15 Sebastian Peryt
>
> gcc/
>
> PR
Hi!
On Sat, Jan 13, 2018 at 10:53:57PM -0600, Bill Schmidt wrote:
> This patch adds a new option for the compiler to produce only "safe" indirect
> jumps, in the sense that these jumps are deliberately mispredicted to inhibit
> speculative execution. For now, this option is undocumented; this
On Mon, Jan 15, 2018 at 4:05 AM, H.J. Lu wrote:
> On Sun, Jan 14, 2018 at 1:23 PM, H.J. Lu wrote:
>> On Sun, Jan 14, 2018 at 10:52 AM, Uros Bizjak wrote:
>>> On Sun, Jan 14, 2018 at 7:08 PM, H.J. Lu wrote:
On Jan 15, 2018, at 11:05 AM, Segher Boessenkool
wrote:
>
> Hi!
>
> On Sun, Jan 14, 2018 at 11:34:06AM -0600, Bill Schmidt wrote:
>> It was pointed out off-list that I should add some executable tests for
>> the new -msafe-indirect-jumps implementation. This patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83817
Jakub Jelinek changed:
What|Removed |Added
Priority|P1 |P2
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83850
Richard Biener changed:
What|Removed |Added
Keywords|ra |
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83852
Richard Biener changed:
What|Removed |Added
Priority|P3 |P1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83855
--- Comment #1 from Richard Biener ---
*** Bug 83854 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83854
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83855
--- Comment #2 from Richard Biener ---
patches should be sent to gcc-patc...@gcc.gnu.org
On 11/01/18 13:41, Richard Biener wrote:
> 2018-01-11 Richard Biener
>
> PR tree-optimization/83435
> * graphite.c (canonicalize_loop_form): Ignore fake loop exit edges.
> * graphite-scop-detection.c (scop_detection::get_sese): Likewise.
> *
Hi!
On Sun, Jan 14, 2018 at 11:34:06AM -0600, Bill Schmidt wrote:
> It was pointed out off-list that I should add some executable tests for
> the new -msafe-indirect-jumps implementation. This patch adds three
> such tests to demonstrate correct behavior.
>
> Tested on powerpc64-linux-gnu and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83864
Bug ID: 83864
Summary: ICE in gfc_apply_init, at fortran/expr.c:4271
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
On Mon, 2018-01-15 at 10:24 +, Richard Sandiford wrote:
> >> + for (int i = 0; i < midpoint; i++)
> >> +{
> >> + tree tmp1 = build_int_cst (lhs_type_type, offset + i);
> >> + tree tmp2 = build_int_cst (lhs_type_type, offset + n_elts +
> i);
> >> + CONSTRUCTOR_APPEND_ELT
Thanks!
Cory
On Jan 15, 2018 1:06 AM, "Jeff Law" wrote:
> On 01/12/2018 01:58 PM, li...@coryfields.com wrote:
> > From: Cory Fields
> >
> > 2018-01-12 Cory Fields
> >* tree-ira.c (allocno_hard_regs_compare):
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83816
--- Comment #9 from Oleg Endo ---
This is weird. If I remove empty lines, or rename the paths in the # line
markers in the .ii file, the error sometimes disappears...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83866
Bug ID: 83866
Summary: [8 Regression] ICE in gfc_release_symbol, at
fortran/symbol.c:3087
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83728
Richard Biener changed:
What|Removed |Added
Priority|P3 |P1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83739
Richard Biener changed:
What|Removed |Added
Priority|P3 |P1
1 - 100 of 392 matches
Mail list logo