On Thu, Feb 8, 2018 at 6:00 PM, Jeff Law wrote:
> On 02/08/2018 04:42 AM, Aldy Hernandez wrote:
> You are a brave soul.
I would've preferred to close as WONTFIX from the gun, but no one
commented, so I tried my hand at a patch :).
>
> Every time I look at 56750 I shake my
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56750
Aldy Hernandez changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84298
--- Comment #2 from Richard Biener ---
The fix is to place a DECL_EXPR somewhere by the FE. We have some duplicates
with similar issues.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84295
Richard Biener changed:
What|Removed |Added
Priority|P3 |P1
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84292
Richard Biener changed:
What|Removed |Added
Target||arm
Status|NEW
Hi,
Here's v3 of the patch to disable register offset addressing mode for
stores of 128-bit values on Falkor because they're very costly.
Following Kyrill's suggestion, I compared the codegen for a53 and
found that the codegen was quite different. Jim's original patch is
the most minimal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84281
--- Comment #5 from fiesh at zefix dot tv ---
The test case was reduced from an actual translation unit that stalled our
build server. Since the translation unit itself was invalid C++, the test case
is too. I think it shouldn't be part of the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84059
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84082
Jakub Jelinek changed:
What|Removed |Added
Summary|[7/8 Regression] ICE with |[7 Regression] ICE with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83659
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84232
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84252
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84237
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84285
--- Comment #6 from Jakub Jelinek ---
Fixed on the trunk so far.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84232
--- Comment #3 from Jakub Jelinek ---
Author: jakub
Date: Fri Feb 9 06:44:43 2018
New Revision: 257516
URL: https://gcc.gnu.org/viewcvs?rev=257516=gcc=rev
Log:
PR tree-optimization/84232
* gcc.dg/tree-ssa/ssa-dom-cse-2.c: Add
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84285
--- Comment #5 from Jakub Jelinek ---
Author: jakub
Date: Fri Feb 9 06:44:06 2018
New Revision: 257515
URL: https://gcc.gnu.org/viewcvs?rev=257515=gcc=rev
Log:
PR sanitizer/84285
* gcc.c (STATIC_LIBASAN_LIBS,
Hi!
BSWAP is documented as:
@item (bswap:@var{m} @var{x})
Represents the value @var{x} with the order of bytes reversed, carried out
in mode @var{m}, which must be a fixed-point machine mode.
The mode of @var{x} must be @var{m} or @code{VOIDmode}.
The fixed-point is something used widely in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84301
Andrew Pinski changed:
What|Removed |Added
Keywords||ice-on-valid-code
On February 9, 2018 7:27:57 AM GMT+01:00, Jakub Jelinek
wrote:
>Hi!
>
>When linking with -static-lib{a,t,l,ub}san -fsanitize=whatever, we link
>-l{a,t,l,ub}san statically into the binary and add the set of libraries
>needed by the lib{a,t,l,ub}san.a afterwards (-lpthread, -ldl
On February 9, 2018 7:31:33 AM GMT+01:00, Jakub Jelinek
wrote:
>Hi!
>
>As mentioned in the PR, DOM/SLP can only handle the case when the
>stores
>of the vector are in the same chunks as the reads from it, so the
>testcase
>has lots of xfails for targets where this doesn't
Hi!
As mentioned in the PR, DOM/SLP can only handle the case when the stores
of the vector are in the same chunks as the reads from it, so the testcase
has lots of xfails for targets where this doesn't happen.
On x86 in the generic and many other tunings the vector is stored in the
same chunks as
Hi!
When linking with -static-lib{a,t,l,ub}san -fsanitize=whatever, we link
-l{a,t,l,ub}san statically into the binary and add the set of libraries
needed by the lib{a,t,l,ub}san.a afterwards (-lpthread, -ldl etc.).
When doing -static -fsanitize=whatever link, we link the sanitizer library
Hi!
When placing a variable length field into a structure, we need to update
rli->offset_align for the next field. We do:
rli->offset_align = MIN (rli->offset_align, desired_align);
which updates it according to the start of that VLA field, the problem is
that if the field doesn't have a size
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84252
--- Comment #7 from Jakub Jelinek ---
Author: jakub
Date: Fri Feb 9 05:48:33 2018
New Revision: 257514
URL: https://gcc.gnu.org/viewcvs?rev=257514=gcc=rev
Log:
PR debug/84252
* var-tracking.c (vt_add_function_parameter): Punt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84237
--- Comment #2 from Jakub Jelinek ---
Author: jakub
Date: Fri Feb 9 05:47:24 2018
New Revision: 257513
URL: https://gcc.gnu.org/viewcvs?rev=257513=gcc=rev
Log:
PR middle-end/84237
* output.h (bss_initializer_p): Add NAMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83659
--- Comment #3 from Jakub Jelinek ---
Author: jakub
Date: Fri Feb 9 05:46:18 2018
New Revision: 257512
URL: https://gcc.gnu.org/viewcvs?rev=257512=gcc=rev
Log:
PR c++/83659
* fold-const.c (fold_indirect_ref_1): Use
This PR is one of those with a really obvious cause, and fix. There's
nothing in the unspec rtl to say the insn needs lr!
Bootstrapped and regression tested powerpc64le-linux. OK?
PR target/84300
gcc/
* config/rs6000/rs6000.md (split_stack_return): Use LR.
gcc/testsuite/
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84303
Bug ID: 84303
Summary: Styled quotes in error message may be inappropriate
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
On Wed, 2018-02-07 at 19:26 -0500, Paul Smith wrote:
> Thanks for the conversation. I'm moving forward with a real global
> operator new/delete and working out the magic needed to ensure those
> symbols are not global in our shared library.
I remember one annoying thing I ran into: through
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84302
Bug ID: 84302
Summary: ICE: Segmentation fault (in extract_insn) on SPE
target
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: ice-on-valid-code
On 02/08/2018 08:53 PM, Alan Modra wrote:
> On Fri, Feb 09, 2018 at 01:21:27AM -0200, Alexandre Oliva wrote:
>> Here's what I checked in, right after the LVU patch.
>>
>> [IEPM] Introduce inline entry point markers
>
> One of these two patches breaks ppc64le bootstrap with the assembler
>
On Fri, Feb 09, 2018 at 01:21:27AM -0200, Alexandre Oliva wrote:
> Here's what I checked in, right after the LVU patch.
>
> [IEPM] Introduce inline entry point markers
One of these two patches breaks ppc64le bootstrap with the assembler
complaining "Error: view number mismatch" when compiling
On Feb 8, 2018, Jason Merrill wrote:
> On Thu, Feb 8, 2018 at 7:56 AM, Alexandre Oliva wrote:
>> On Feb 7, 2018, Jason Merrill wrote:
>>
>>> OK, that makes sense. But I'm still uncomfortable with choosing an
>>> existing opcode for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84301
Bug ID: 84301
Summary: ICE in create_pre_exit, at mode-switching.c:451
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: ice-checking
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84300
Alan Modra changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned at
On Jan 25, 2018, Alexandre Oliva wrote:
> On Jan 24, 2018, Jakub Jelinek wrote:
>> I think this asks for
>> if (flag_checking)
>> gcc_assert (block_within_block_p (block,
>> DECL_INITIAL (current_function_decl),
>> true));
> 'k, changed.
>> Otherwise the
On Feb 8, 2018, Jason Merrill wrote:
> On 02/07/2018 02:36 AM, Alexandre Oliva wrote:
>> +/* Output symbol LAB1 as an unsigned LEB128 quantity. */
> Let's mention here that the value of LAB1 must be an assemble-time
> constant (such as a view counter), since we can't have
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84300
Alan Modra changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84208
--- Comment #5 from Akhilesh Kumar ---
Please Mark this bug ID as invalid with the same patch I am able to run on ARM
also there was issue in My setup only (Sorry for the noise).
Test results on ARM (gcc 6.2.1)
sh-3.2# out_of_scope
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84207
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
Ping: https://gcc.gnu.org/ml/gcc-patches/2018-02/msg00076.html
On 02/01/2018 04:45 PM, Martin Sebor wrote:
The previous patch didn't resolve all the false positives
in the Linux kernel. The attached is an update that fixes
the remaining one having to do with multidimensional array
members:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84256
Martin Sebor changed:
What|Removed |Added
Keywords||diagnostic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84231
Alexandre Oliva changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #4 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84300
Bug ID: 84300
Summary: ICE in dwarf2cfi on ppc64le with -fsplit-stack
-fno-omit-frame-pointer
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
A non-type-dependent COND_EXPR within a template is reconstructed with
the original operands, after one with non-dependent proxies is built to
determine its result type. This is problematic because the operands of
a COND_EXPR determined to be an rvalue may have been converted to denote
their
On Feb 8, 2018, at 12:36 PM, Segher Boessenkool
wrote:
>
> On Wed, Feb 07, 2018 at 03:52:27PM -0800, Mike Stump wrote:
>> I dusted the pointed to patch off and check it in. Let us know how it goes.
>
> I wanted to test this on the primary and secondary powerpc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84136
David Malcolm changed:
What|Removed |Added
Summary|[6/7/8 Regression] ICE with |[6/7 Regression] ICE with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84136
--- Comment #4 from David Malcolm ---
Author: dmalcolm
Date: Fri Feb 9 01:07:11 2018
New Revision: 257509
URL: https://gcc.gnu.org/viewcvs?rev=257509=gcc=rev
Log:
Fix ICE in find_taken_edge_computed_goto (PR 84136)
PR 84136 reports an ICE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84281
Martin Sebor changed:
What|Removed |Added
Keywords||error-recovery,
|
On 02/08/2018 05:39 PM, Ian Lance Taylor wrote:
On Thu, Feb 8, 2018 at 3:24 PM, Martin Sebor wrote:
While testing what should be an innocuous patch to add LTO
to a bunch of middle-end warning options
https://gcc.gnu.org/ml/gcc-patches/2018-02/msg00381.html
I get Go
Never mind. I see the problem. I overlooked a few failures
in the preprocessor test suite. Turns out the patch accidentally
deletes the -d option from the .opt file. I didn't notice it in
the diff because the "-d" at the beginning of the line looks just
like the option is still there!
@@
On Thu, Feb 8, 2018 at 3:24 PM, Martin Sebor wrote:
>
> While testing what should be an innocuous patch to add LTO
> to a bunch of middle-end warning options
>
> https://gcc.gnu.org/ml/gcc-patches/2018-02/msg00381.html
>
> I get Go errors during ordinary bootstrap about
On Thu, Feb 08, 2018 at 06:10:31PM -0500, Hans-Peter Nilsson wrote:
> On Wed, 7 Feb 2018, Segher Boessenkool wrote:
> > Hi Mike,
> >
> > On Tue, Feb 06, 2018 at 04:34:08PM -0500, Michael Meissner wrote:
> > > Here is the patch reworked. It bootstraps on both little/big endian
> > > power8,
> > >
Hi!
On Wed, Feb 07, 2018 at 09:14:59AM -0600, Will Schmidt wrote:
> Our VEC_SLD definitions were mistakenly allowing the third argument to be
> of an invalid type, triggering an ICE (on invalid code) later in the build
> process. This fixes those definitions. The nearby VEC_SLDW definitions
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84287
Martin Sebor changed:
What|Removed |Added
Keywords||rejects-valid
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81824
--- Comment #8 from Martin Sebor ---
I see. I think you are specifically talking about the case when the three
attributes are used together, as in:
void __attribute__ ((weak, alias ("__foo"), visibility ("..."))) foo ();
void __foo () {
On 02/07/2018 03:43 PM, Jakub Jelinek wrote:
> Hi!
>
> As mentioned in the PR, the vt_get_decl_and_offset function verifies
> incoming PARALLEL is usable for tracking, but if it fails, we retry
> vt_get_decl_and_offset on DECL_RTL and there we check only that a memory
> isn't larger than 16 bytes
Hi Ian,
While testing what should be an innocuous patch to add LTO
to a bunch of middle-end warning options
https://gcc.gnu.org/ml/gcc-patches/2018-02/msg00381.html
I get Go errors during ordinary bootstrap about undefined names
for errno constants:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81824
--- Comment #7 from joseph at codesourcery dot com ---
On Thu, 8 Feb 2018, msebor at gcc dot gnu.org wrote:
> Okay, that would make sense. But then what do you mean by "weak, alias,
> visibility attributes are expected to differ between
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79242
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P4
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71361
--- Comment #9 from Jeffrey A. Law ---
Leslie, you'd need to bisect. Probably something from Bin in the summer of
2017. Not something we're likely to backport.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81824
--- Comment #6 from Martin Sebor ---
Okay, that would make sense. But then what do you mean by "weak, alias,
visibility attributes are expected to differ between different names and
shouldn't be diagnosed."
The example in comment #0 shows a
On 02/06/2018 01:44 PM, Jakub Jelinek wrote:
> Hi!
>
> The last year's bss_initializer_p change apparently broke xen. While it is
> reasonable not to put const variables into .bss* sections by default,
> refusing to put them when the user asks for it through using section
> attribute seems
On Wed, 7 Feb 2018, Segher Boessenkool wrote:
> Hi Mike,
>
> On Tue, Feb 06, 2018 at 04:34:08PM -0500, Michael Meissner wrote:
> > Here is the patch reworked. It bootstraps on both little/big endian power8,
> > and all of the tests run. Can I install this into trunk now, and into GCC 7
> > after
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43361
Manuel López-Ibáñez changed:
What|Removed |Added
CC||daffra.claudio at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84289
Manuel López-Ibáñez changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
On 02/08/2018 04:42 AM, Aldy Hernandez wrote:
> In this PR, the reporter is complaining that forcing -static-libstdc++
> and -static-libgcc during stage1 will also force it down to all
> subdirectories (gdb for instance).
>
> There is some back and forth in the PR whether this is good or not.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77522
Paolo Carlini changed:
What|Removed |Added
CC||dmalcolm at gcc dot gnu.org,
On Thu, Feb 8, 2018 at 6:11 PM, Kyrill Tkachov
wrote:
> Hi all,
>
> This patch fixes some fallout in the i386 testsuite that occurs after the
> simplification in patch [1/3] [1].
> The gcc.target/i386/extract-2.c FAILs because it expects to match:
> (set (reg:CC 17
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81824
--- Comment #5 from joseph at codesourcery dot com ---
In the case most likely to appear in glibc, foo would be declared with the
nothrow attribute and __foo would be missing it. I see no reason not to
diagnose the other case as well, I just
Hi,
On 9 February 2018 at 09:08, Steve Ellcey wrote:
> I have a question about the poly_uint64 type and the TYPE_VECTOR_SUBPARTS
> macro. I am trying to copy some code from i386.c into my aarch64 build
> that is basically:
>
> int n;
> n = TYPE_VECTOR_SUBPARTS (type_out);
>
Snapshot gcc-7-20180208 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/7-20180208/
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/branches/gcc-7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81824
--- Comment #4 from Martin Sebor ---
(In reply to Joseph S. Myers from comment #0)
> Note: this warning is only for attributes relating to the function itself,
> not to those relating to a particular name for the function. For example,
> weak,
On Thu, Feb 8, 2018 at 12:48 PM, Shalnov, Sergey
wrote:
> Hi,
> This patch contain cost model change for SKX and closes PR target/83008
> (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83008)
>
> It provides following performance scores in geomean:
> SPEC CPU2017 intrate
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83008
--- Comment #37 from uros at gcc dot gnu.org ---
Author: uros
Date: Thu Feb 8 22:31:15 2018
New Revision: 257505
URL: https://gcc.gnu.org/viewcvs?rev=257505=gcc=rev
Log:
PR target/83008
* config/i386/x86-tune-costs.h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84178
--- Comment #5 from David Malcolm ---
Candidate patch/RFC:
https://gcc.gnu.org/ml/gcc-patches/2018-02/msg00468.html
PR tree-optimization/84178 reports a couple of source files that ICE inside
ifcvt when compiled with -03 -fno-tree-forwprop (trunk and gcc 7).
Both cases involve problems with ifcvt's per-BB gimplified predicates.
Testcase 1 fails this assertion within release_bb_predicate during cleanup:
283
I have a question about the poly_uint64 type and the TYPE_VECTOR_SUBPARTS
macro. I am trying to copy some code from i386.c into my aarch64 build
that is basically:
int n;
n = TYPE_VECTOR_SUBPARTS (type_out);
And it is not compiling for me, I get:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83723
--- Comment #4 from Jakub Jelinek ---
Matthias, can you reproduce this with current trunk and if so, do you have
unreduced preprocessed testcase + options?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83503
Martin Sebor changed:
What|Removed |Added
Keywords||patch
--- Comment #19 from Martin Sebor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84299
Bug ID: 84299
Summary: warning: '' may be used uninitialized in
this function
Product: gcc
Version: 8.0.1
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83871
Martin Sebor changed:
What|Removed |Added
Keywords||patch
--- Comment #2 from Martin Sebor
__attribute__ ((nothrow))? The patch includes a test case with
wrong-code due to inheriting the attribute. With exception
specifications having to match between the primary and its
specializations it's the only way to make them different.
I've left this unchanged but let me know if I'm missing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81635
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84298
Bug ID: 84298
Summary: Shared TYPE_SIZE_UNIT ends up with freed SSA names
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84298
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84265
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Fed to any verison of GCC, I get something like the following.
In file included from :1:
/opt/compiler-explorer/gcc-trunk-20180208/include/c++/8.0.1/type_traits: In
instantiation of 'struct std::is_trivially_constructible<S, int&()>':
:5:48: required from here
/opt/compiler-explore
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84277
Eric Botcazou changed:
What|Removed |Added
Status|WAITING |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84173
--- Comment #14 from Javier Serrano Polo
---
(In reply to Adam Conrad from comment #13)
> Please stop speaking as if you speak for the Debian toolchain maintainers,
> or Debian as a whole. You don't.
I do not represent Debian, but I state
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78303
kelvin at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81143
Peter Bergner changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #4 from Peter
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81143
Peter Bergner changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
URL|
On 02/08/2018 03:38 AM, Richard Biener wrote:
On Thu, Feb 1, 2018 at 6:42 PM, Aldy Hernandez wrote:
Since my patch isn't the easy one liner I wanted it to be, perhaps we
should concentrate on Martin's patch, which is more robust, and has
testcases to boot! His patch from
I have committed the following obvious testsuite patch to fix PR81143.
The "bug" is that __ORDER_LITTLE_ENDIAN__ is always defined for both
little and big endian compiles. I checked and this is the only use
of this in the gcc.target/powerpc/ directory.
Peter
PR target/81143
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80865
Segher Boessenkool changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81143
--- Comment #2 from Peter Bergner ---
Author: bergner
Date: Thu Feb 8 20:40:32 2018
New Revision: 257504
URL: https://gcc.gnu.org/viewcvs?rev=257504=gcc=rev
Log:
PR target/81143
* gcc.target/powerpc/pr79799-2.c: Use
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84296
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84296
Bug ID: 84296
Summary: [8 Regression] ICE in finish_member_declaration
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84280
--- Comment #14 from Patrik Huber ---
It even seems a few percent slower after the FDO stuff. But the `
-fprofile-use` is a bit weird. If there is no .gcda file, it doesn't complain.
If you give it a file that doesn't exist (e.g.
1 - 100 of 359 matches
Mail list logo