Hi Jerry and Steve,
OK for trunk.
OK.
Regards
Thomas
On 02/22/2016 02:22 AM, Bin.Cheng wrote:
My only question is why didn't you use FOR_EACH_SUBRTX_VRA from rtl-iter.h
to walk the RTX expressions in collect_address_parts and
canonicalize_address_mult?
Hi Jeff,
Nothing special, just I haven't used this before, also
canonicalize_address_mult is
On 02/22/2016 02:26 PM, Jakub Jelinek wrote:
Hi!
The following testcase is miscompiled, because prepare_shrink_wrap
attempts to copyprop_hardreg_forward_1 the first bb. We see
DImode rbx being copied to DImode r11, and then we have (dead since
postreload) an assignment of SImode r11d to SImode
PR69740 shows two instances where one or more transformations ultimately
lead to the removal of a basic block.
In both cases, removal of the basic block removes a path into an
irreducible region and turns the irreducible region into a natural loop.
When that occurs we need to be requesting
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69740
--- Comment #5 from Jeffrey A. Law ---
The testcase in c#3 is another instance of this problem, but triggered by
sinking. I'd already been pondering the benefit/risk of attacking this at a
higher level (like in delete_basic_block) and seeing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69564
Patrick Palka changed:
What|Removed |Added
CC||ppalka at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69899
David changed:
What|Removed |Added
CC||gccbugzilla@limegreensocks.
|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69952
Bug ID: 69952
Summary: ICE with a long double vector
Product: gcc
Version: 4.8.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21106
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
--enable-languages=c,c++ --disable-werror --enable-multilib
Thread model: posix
gcc version 6.0.0 20160224 (experimental) [trunk revision 233678] (GCC)
$ gcc-trunk abc.c
$ ./a.out
$ gcc-trunk -O1 abc.c
$ ./a.out
Aborted (core dumped)
$ cat abc.c
int a = 1, c = 1;
extern int b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69736
Patrick Palka changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69736
--- Comment #8 from Patrick Palka ---
Author: ppalka
Date: Thu Feb 25 01:14:27 2016
New Revision: 233691
URL: https://gcc.gnu.org/viewcvs?rev=233691=gcc=rev
Log:
Fix PR c++/69736
gcc/cp/ChangeLog:
PR c++/69736
* cp-tree.h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69910
--- Comment #6 from Jerry DeLisle ---
Patch submiited:
https://gcc.gnu.org/ml/fortran/2016-02/msg00095.html
This patch from Steve on c.l.f
Fixes the segfault from attempting a string compare where there is no string
yet.
Regression tested on x86-64. New test case.
OK for trunk.
Regards,
Jerry
2016-02-24 Jerry DeLisle
Steven G. Kargl
On Wed, Feb 24, 2016 at 3:38 PM, Joseph Myers wrote:
> On Wed, 24 Feb 2016, Wink Saville wrote:
>
>> > (c) nothing defines semantics of conversion of out-of-range values to
>> > bit-fields other than treating the width as part of the type (or in the
>> > case of _Bool
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=23093
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
On Wed, 24 Feb 2016, Wink Saville wrote:
> > (c) nothing defines semantics of conversion of out-of-range values to
> > bit-fields other than treating the width as part of the type (or in the
> > case of _Bool bit-fields, having the special wording to make it explicit
> > that those have the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49459
Martin Sebor changed:
What|Removed |Added
Last reconfirmed|2011-06-17 18:56:47 |2016-2-24
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51147
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51147
--- Comment #4 from Martin Sebor ---
Author: msebor
Date: Wed Feb 24 23:26:42 2016
New Revision: 233686
URL: https://gcc.gnu.org/viewcvs?rev=233686=gcc=rev
Log:
PR c/51147 - attribute((mode(byte))) on an enum generates wrong code
See comment on (c) below
On Wed, Feb 24, 2016 at 1:53 PM Joseph Myers wrote:
>
> On Wed, 24 Feb 2016, Martin Sebor wrote:
>
> > > That can be avoided simply by using unary + in the controlling expression
> > > of _Generic (just as using unary + will avoid an error from
Thomas Schwinge, on Wed 24 Feb 2016 23:46:36 +0100, wrote:
> I guess getting -D_REENTRANT for -pthread won't do us any harm?
It won't.
> > --- gcc/config/i386/gnu.h.orig 2015-09-17 21:41:13.0 +
> > +++ gcc/config/i386/gnu.h 2015-09-17 23:03:57.0 +
> > @@ -27,11
On Wed, 2016-02-24 at 13:46 -0800, Matthew Fortune wrote:
> Thanks for enumerating all the cases. I'd not looked at all of them. I
> do agree that we need a fix given the existing inconsistencies.
>
> One question I have is where does an over aligned argument get pushed
> to the stack with the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69950
Bug ID: 69950
Summary: Allow more than one exit phi for reduction in
try_create_reduction_list
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: minor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69949
Bug ID: 69949
Summary: Optimally handle case that outer phi res is not used
in a phi in gather_scalar_reductions
Product: gcc
Version: 6.0
Status: UNCONFIRMED
This patch adds support for builtin overflow of add, subtract and
negate. This patch is targeted for gcc 7 stage 1. It was tested with no
regressions in arm and thumb modes on the following targets:
arm-non-linux-gnueabi
arm-non-linux-gnuabihf
armeb-none-linux-gnuabihf
arm-non-eabi
2016-02-24
Some DImode rotate-right-and-mask can be implemented best with a rlwinm
instruction: those that could be a lshiftrt instead of a rotatert, while
the mask is not right-aligned. Why the rotate in the testcase is not
optimised to a plain shift is another question, but we need to handle
it here
Hi!
Sorry for the late answer...
On Sat, 19 Sep 2015 14:00:23 +0200, Samuel Thibault
wrote:
> On Linux, -p and -pg do not make gcc link against libc_p.a, only
> -profile does (as documented in r11246), and thus people expect -p
(Yo, 20 years ago...)
> and -pg to work
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69945
--- Comment #1 from Mark Wielaard ---
See also this valgrind bug: https://bugs.kde.org/show_bug.cgi?id=345307
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69948
Bug ID: 69948
Summary: Parallelize loops containing phis with addr_exprs
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: minor
Priority: P3
Component:
Snapshot gcc-4.9-20160224 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.9-20160224/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.9 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69705
Jakub Jelinek changed:
What|Removed |Added
Summary|[5/6 Regression] segfault |[5 Regression] segfault in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69922
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69705
--- Comment #3 from Jakub Jelinek ---
Author: jakub
Date: Wed Feb 24 22:04:09 2016
New Revision: 233685
URL: https://gcc.gnu.org/viewcvs?rev=233685=gcc=rev
Log:
PR debug/69705
* dwarf2out.c (gen_variable_die): Work around buggy
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69922
--- Comment #6 from Jakub Jelinek ---
Author: jakub
Date: Wed Feb 24 22:01:24 2016
New Revision: 233684
URL: https://gcc.gnu.org/viewcvs?rev=233684=gcc=rev
Log:
PR c++/69922
* class.c (build_base_path): Set TREE_NO_WARNING on
On 02/23/2016 04:56 AM, Richard Biener wrote:
On Mon, Feb 22, 2016 at 4:34 PM, Jeff Law wrote:
On 02/22/2016 07:34 AM, Richard Biener wrote:
Hum, but then you get to "inifinite" compiles again when LRA is buggy
or the user presents it with an impossible to handle asm.
On Wed, 24 Feb 2016, Steve Ellcey wrote:
> I also added a way to turn that warning off in case the user doesn't
> want to see it (-mno-warn-aligned-args). I did not add an option
Any command-line options need documenting in invoke.texi.
--
Joseph S. Myers
jos...@codesourcery.com
On Wed, 24 Feb 2016, Martin Sebor wrote:
> > That can be avoided simply by using unary + in the controlling expression
> > of _Generic (just as using unary + will avoid an error from sizeof, if you
> > want to be able to apply that to expressions that might be bit-fields) -
> > or any of the
The previous gcov behavior was to always output errors on the stderr channel.
This is fine for most uses, but some programs will require stderr to be
untouched by libgcov for certain tests. This change allows configuring
the gcov output via an environment variable which will be used to open
the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69819
Marek Polacek changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69819
--- Comment #6 from Marek Polacek ---
Author: mpolacek
Date: Wed Feb 24 21:47:59 2016
New Revision: 233683
URL: https://gcc.gnu.org/viewcvs?rev=233683=gcc=rev
Log:
PR c/69819
* c-decl.c (finish_decl): Don't update the copy of
Steve Ellcey writes:
> Here is a new patch for PR 68273. The original problem with gsoap has
> been fixed by changing GCC to not create overly-aligned variables in
> the SRA pass but the MIPS specific problem of how user-aligned variables
> are passed to functions remains.
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68659
vries at gcc dot gnu.org changed:
What|Removed |Added
CC||vries at gcc dot gnu.org
---
OK.
Jason
On 02/24/2016 10:25 AM, Jakub Jelinek wrote:
That should be @option{-flifetime-dse=1} I think. Shouldn't -flifetime-dse=
be also in @opindex at the beginning of the paragraph, and documented what
the values mean (0 equivalent of -fno-lifetime-dse (or document it vice
versa) and 2 full lifetime
On 02/24/2016 03:05 PM, Jakub Jelinek wrote:
On Wed, Feb 24, 2016 at 02:57:49PM -0500, Jason Merrill wrote:
On 02/24/2016 02:05 PM, Jakub Jelinek wrote:
+ && integer_zerop (tree_strip_nop_conversions (TREE_OPERAND (org_x,
+
OK.
Jason
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68049
Jason Merrill changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69125
Jason Merrill changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69839
--- Comment #5 from Jakub Jelinek ---
Likely a bug on the Gentoo side.
The linker handles differently libraries specified on the command line and
libraries that are needed by those shared libraries, but are not mentioned on
the command line.
Hi,
A quick note to see if you would be interested in a discussion about RSA List
and the benefits it can bring your organization for your Marketing Initiatives.
Every contact will include: Company Name, Web Address, Contact Name, Verified
Email, Job Title, Application Type, Complete Mailing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69323
Jason Merrill changed:
What|Removed |Added
Keywords|ice-on-valid-code |ice-on-invalid-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60126
--- Comment #4 from Harald Anlauf ---
For a simple testcase that can be added to the trunk see
https://gcc.gnu.org/ml/fortran/2016-02/msg00092.html
On 02/24/2016 01:42 PM, Alexander Monakov wrote:
On Wed, 24 Feb 2016, DJ Delorie wrote:
The real question is: are stack arguments call-clobbered or
call-preserved? Does the answer depend on the "pure" attribute?
Stack area holding stack arguments should belong to the callee for tail-calls
to
On 02/24/16 20:42, Harald Anlauf wrote:
> Hello,
>
> the above bug appears to have been fixed over 2.5 years ago.
> It does not trigger with 4.9, 5 and 6 trunk, but does with 4.8.0 and
> before.
>
> I recommend to close the bug, while adding a testcase to the trunk's
> testsuite. See e.g. the
On Wed, 24 Feb 2016, DJ Delorie wrote:
> The real question is: are stack arguments call-clobbered or
> call-preserved? Does the answer depend on the "pure" attribute?
Stack area holding stack arguments should belong to the callee for tail-calls
to work (the callee will trash that area when
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69947
Bug ID: 69947
Summary: [6 Regression] DW_OP_GNU_implicit_pointer broken on
the trunk
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Keywords: wrong-debug
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69947
Jakub Jelinek changed:
What|Removed |Added
Priority|P3 |P1
Target Milestone|---
Jakub,
this patch fixes the ICE reported in pr69916
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69916) The loop is lowered at
omp-lowering, but subsequently determined to be dead before we get to
oacc-target-lower. The loop CF is removed along with the (pure) IFN_OACC_LOOP
function calls
On Wed, Feb 24, 2016 at 02:57:49PM -0500, Jason Merrill wrote:
> On 02/24/2016 02:05 PM, Jakub Jelinek wrote:
> >+ && integer_zerop (tree_strip_nop_conversions (TREE_OPERAND (org_x,
> >+ 1
>
> Why check this? I think we
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69323
--- Comment #8 from Jason Merrill ---
Author: jason
Date: Wed Feb 24 19:56:09 2016
New Revision: 233682
URL: https://gcc.gnu.org/viewcvs?rev=233682=gcc=rev
Log:
PR c++/69323 - errors
* friend.c (make_friend_class): Likewise.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69740
Jeffrey A. Law changed:
What|Removed |Added
CC||law at redhat dot com
--- Comment #4
On 02/24/2016 02:05 PM, Jakub Jelinek wrote:
+ && integer_zerop (tree_strip_nop_conversions (TREE_OPERAND (org_x,
+ 1
Why check this? I think we want this handling for all TREE_NO_WARNING
comparisons.
Jason
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69323
--- Comment #7 from Jason Merrill ---
Author: jason
Date: Wed Feb 24 19:56:03 2016
New Revision: 233681
URL: https://gcc.gnu.org/viewcvs?rev=233681=gcc=rev
Log:
PR c++/69323 - valid
* pt.c (instantiate_class_template_1): Set
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69323
--- Comment #6 from Jason Merrill ---
Author: jason
Date: Wed Feb 24 19:55:45 2016
New Revision: 233679
URL: https://gcc.gnu.org/viewcvs?rev=233679=gcc=rev
Log:
PR c++/69323 - valid
* pt.c (instantiate_class_template_1): Set
The testcase in the BZ is invalid, but there's a valid variant that also
ICEd. I've fixed the compiler to do the right thing with three
different variants.
Tested x86_64-pc-linux-gnu, applying to trunk. Changes for the valid
variant also applied to 5.
commit
On Wed, 24 Feb 2016, Jason Merrill wrote:
On 02/23/2016 11:24 AM, Patrick Palka wrote:
1. making tsubst_copy_and_build retain the REF_PARENTHESIZED_P flag when
processing an INDIRECT_REF, or by
This should happen in any case.
2. moving the call to maybe_undo_parenthesized_ref in
Hello,
the above bug appears to have been fixed over 2.5 years ago.
It does not trigger with 4.9, 5 and 6 trunk, but does with 4.8.0 and
before.
I recommend to close the bug, while adding a testcase to the trunk's
testsuite. See e.g. the attached example.
Harald
2016-02-24 Harald Anlauf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69811
Jeffrey A. Law changed:
What|Removed |Added
CC||law at redhat dot com
--- Comment #6
$ cat z.c && /home/msebor/build/gcc-trunk-svn/gcc/xgcc
-B/home/msebor/build/gcc-trunk-svn/gcc -Wall -Wextra -Wpedantic -xc z.c
struct S { unsigned i: 31; } s;
int i = _Generic (s.i, unsigned: 1);
z.c:2:19: error: ‘_Generic’ selector of type ‘unsigned int:31’ is not
compatible with any association
On Wed, Feb 24, 2016 at 10:29:47PM +0300, Ilya Verbin wrote:
> Done.
> Here is a follow up patch. OK for trunk? Bootstrapped and regtested.
Ok with appropriate ChangeLog entry.
Jakub
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69920
Jeffrey A. Law changed:
What|Removed |Added
CC||chengniansun at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69936
Jeffrey A. Law changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69924
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69920
Jeffrey A. Law changed:
What|Removed |Added
CC||ubizjak at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69938
Jeffrey A. Law changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On Mon, Feb 22, 2016 at 16:13:07 +0100, Thomas Schwinge wrote:
> (..., and similar for others.) The if-exists spec function only works
> for absolute paths (I have not researched, why?), so it won't locate the
> files for relative -Bbuild-gcc/[...] prefixes, and linking will fail:
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69927
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org,
Consider this example (derived from gcc.c-torture/execute/920726-1.c):
extern int a(int a, int b, int c, int d, int e, int f, const char *s1, const
char *s2) __attribute__((pure));
int
foo()
{
if (a(0,0,0,0,0,0,"abc","def") || a(0,0,0,0,0,0,"abc","ghi"))
return 0;
return
Hi!
This is something that I hope early debug for LTO will eventually
fix, but we aren't there yet and current trunk emits bogus debug info
for inlines - DW_TAG_subprogram of the inline doesn't contain any
parameters/variables/lexical blocks etc. in it, but in
DW_TAG_inlined_subroutine we add all
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69868
Bill Schmidt changed:
What|Removed |Added
Attachment #37759|0 |1
is obsolete|
Hi!
This patch adds TREE_NO_WARNING to two places that didn't have it before
and avoids folding those conditions at those spots (partly to match
C++ delayed folding intent, partly to avoid duplicating TREE_NO_WARNING
propagation).
The more controversial stuff is that we need to preserve
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69924
Daniel Krügler changed:
What|Removed |Added
CC||daniel.kruegler@googlemail.
Here is a new patch for PR 68273. The original problem with gsoap has
been fixed by changing GCC to not create overly-aligned variables in
the SRA pass but the MIPS specific problem of how user-aligned variables
are passed to functions remains.
Because MIPS GCC is internally inconsistent, it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69938
--- Comment #6 from Jeffrey A. Law ---
So we have these statements during SRA:
_4 = e[d.1_3];
_5 = (int) _4;
We delete the first statement, presumably because we're going to apply SRA to
the RHS of that statement. That releases _4 back to
This adds a new function to libsupc++ which will free the memory still
in use by the pool used for allocating exceptions when malloc fails.
This is similar to glibc's __libc_freeres, which valgrind (and other
tools?) use to tell glibc to deallocate everything before exiting.
I initially called
On Wed, 24 Feb 2016, Marek Polacek wrote:
> This is a minor issue in the C FE, where it on an invalid code generated bogus
> FUNCTION_DECL with ARRAY_TYPE as a type -- and gimplifier can't digest that.
>
> I think the code in finish_decl, whereby we update the type of shadowed global
> variables
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69946
Segher Boessenkool changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69938
--- Comment #5 from Jeffrey A. Law ---
The released name comes from tree-ssa:
{
if (access_has_children_p (racc)
&& !racc->grp_unscalarized_data)
{
if (dump_file)
{
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69938
Jeffrey A. Law changed:
What|Removed |Added
CC||law at redhat dot com
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69946
--- Comment #1 from Jakub Jelinek ---
To me this looks like the bug is in the analysis function not matching what the
output function does.
rs6000_is_valid_shift_mask
has code like:
17346 /* Convert any shift by 0 to a rotate, to simplify
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69884
--- Comment #4 from Jason Merrill ---
The compiler is letting you know that within A<__m128> the __may_alias__
attribute is discarded, which may lead to unexpected results. Since that
attribute doesn't affect type identity, so it isn't
On Wed, 24 Feb 2016, Richard Earnshaw (lists) wrote:
> After discussion with the ARM port maintainers we have decided that now
> is probably the right time to deprecate support for versions of the ARM
> Architecture prior to ARMv4t. This will allow us to clean up some of
Should this include
On Wed, 24 Feb 2016, Richard Earnshaw (lists) wrote:
> After discussion with the ARM port maintainers we have decided that now
> is probably the right time to deprecate support for versions of the ARM
> Architecture prior to ARMv4t. This will allow us to clean up some of
Should this include
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69927
--- Comment #4 from Markus Trippelsdorf ---
Should be:
markus@x4 tmp % /usr/x86_64-pc-linux-gnu/gcc-bin/4.9.3/gcc -w -march=haswell
-m32 -O3 -c vf_dejudder.i
vf_dejudder.i: In function ‘filter_frame’:
vf_dejudder.i:16:1: internal compiler
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69927
Markus Trippelsdorf changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69912
Martin Sebor changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69912
--- Comment #2 from Martin Sebor ---
Author: msebor
Date: Wed Feb 24 17:23:35 2016
New Revision: 233678
URL: https://gcc.gnu.org/viewcvs?rev=233678=gcc=rev
Log:
PR c++/69912 - [6 regression] ICE in build_ctor_subob_ref initializing
a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69946
Jakub Jelinek changed:
What|Removed |Added
Priority|P3 |P1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69946
Bug ID: 69946
Summary: [6 Regression] Invalid ppc64 assembly emitted starting
with r226005
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
1 - 100 of 244 matches
Mail list logo