https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78875
Bug ID: 78875
Summary: -fstack-protector on powerpc64 now always use TLS,
won't work for kernel/firmware
Product: gcc
Version: 6.2.0
Status: UNCONFIRMED
On Tue, Dec 20, 2016 at 11:31 AM, FX wrote:
>> I don't understand. Why would it imply a 1:1 mapping of release series
>> with major ABI versions?
>
> OK, I thought you meant to map libgfortran version numbers (libgfortran.so.7
> with GCC 7). If it’s the gfortran.map node
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78749
Jason Merrill changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78767
Jason Merrill changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78516
--- Comment #21 from Peter Bergner ---
(In reply to Peter Bergner from comment #20)
> Vlad, for the following change in the hunk above:
>
> > new_reg != NULL_RTX ? sreg : src,
>
> shouldn't that always be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78874
Bug ID: 78874
Summary: Manual describes "-Wno-aggressive-loop-optimizations"
as if without "no-"
Product: gcc
Version: 6.2.1
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77767
--- Comment #8 from Jakub Jelinek ---
Author: jakub
Date: Wed Dec 21 00:07:49 2016
New Revision: 243832
URL: https://gcc.gnu.org/viewcvs?rev=243832=gcc=rev
Log:
PR c/77767
* c-decl.c (grokdeclarator): If *expr is non-NULL,
On Tue, 20 Dec 2016, Jakub Jelinek wrote:
> Hi!
>
> We only record side-effects from the last parameter, the following patch
> fixes that by accumulating them from all the parameters. I've checked all
> the callers of grokdeclarator and grokdeclarator is always called with expr
> either
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78516
--- Comment #20 from Peter Bergner ---
(In reply to Peter Bergner from comment #19)
> emit_insn (GEN_FCN (sri.icode) (new_reg != NULL_RTX ? new_reg : dest,
> new_reg != NULL_RTX ? sreg : src,
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78873
Bug ID: 78873
Summary: Virtual call after conversion to base class pointer is
not devirtualized
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71444
--- Comment #2 from Jonathan Wakely ---
In fact it looks like the patch should work for mingw-w64 v4, and maybe v3 too.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78870
--- Comment #3 from Jonathan Wakely ---
(In reply to Jan Niklas Hasse from comment #2)
> I'm willing to help.
Great! Please read
https://gcc.gnu.org/onlinedocs/libstdc++/manual/appendix_contributing.html
especially the part about legal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78842
Jonathan Wakely changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78872
Jonathan Wakely changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
Snapshot gcc-5-20161220 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/5-20161220/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 5 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78516
--- Comment #19 from Peter Bergner ---
(In reply to Peter Bergner from comment #18)
> With the patch Vlad attached minus the one unwanted line/typo, I'm getting
> an ICE on a powerpc64le-linux bootstrap. Looking into it.
Here's a minimal test
On Tue, Dec 20, 2016 at 10:26:13PM +0100, Dominik Vogt wrote:
> On Tue, Dec 20, 2016 at 11:57:52AM -0800, Mike Stump wrote:
> > On Dec 20, 2016, at 6:10 AM, Dominik Vogt wrote:
> > > Right, it gets called even more often than one would think, and
> > > even with empty
The problem here is that we don't have complete coverage of lea patterns
for HImode/QImode: the combiner can't recognize a (plus (ashift reg 2)
reg) pattern it builds.
My first idea was to canonicalize ASHIFT by constant inside PLUS to
MULT. The docs say that this is done only inside a MEM
On Tue, Dec 20, 2016 at 11:57:52AM -0800, Mike Stump wrote:
> On Dec 20, 2016, at 6:10 AM, Dominik Vogt wrote:
> > Right, it gets called even more often than one would think, and
> > even with empty torture_current_options. The attached new patch
> > (v3) removes -Ox
Hi!
We only record side-effects from the last parameter, the following patch
fixes that by accumulating them from all the parameters. I've checked all
the callers of grokdeclarator and grokdeclarator is always called with expr
either pointing to NULL_TREE, or being NULL, or where we want the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78842
--- Comment #6 from Jim Michaels ---
(In reply to Nathan Sidwell from comment #4)
> sigh, bugzilla's moving on to 'random' other bug gets me. Again.
btw, I think that random bug number feature is in preferences.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78842
--- Comment #5 from Jim Michaels ---
I am going to have to go digging through my code. the function that I had this
error on about icase shadowing a parameter was a global var, and I tried
#include
#include
#include
bool icase=false;
Tested on Linux-x64.
The issue doesn't have a proposed resolution yet, so we can certainly wait
with this, but I have an inkling that this implementation is what the proposed
resolution must say. :)
2016-12-20 Ville Voutilainen
Implement 2801,
On Tue, Dec 20, 2016 at 09:30:17PM +0100, Marc Glisse wrote:
> would it make sense to extend it to rotates later?
I wasn't 100% sure if rotates also require 0..prec-1 rotate counts, or
if they accept arbitrary ones.
> Note that you can write (shift @0 SSA_NAME@1) in the pattern instead of a
>
On Tue, 20 Dec 2016, Jakub Jelinek wrote:
If the shift count has enough known zero low bits (non-zero bits only
above the ceil_log2 (precision)), then the only valid shift count that
is not out of bounds is 0, so we can as well fold it into the first
argument of the shift. This resolves a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78872
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52192
--- Comment #5 from Jonathan Wakely ---
Should we change the target to *-*-netbsd* now that solaris 8 and 9 are not
supported?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78872
--- Comment #1 from Jim Michaels ---
icompare.cpp:12:119: error: no 'int std::locale::icompare(const char_type*,
const char_type*, const char_type*, const char_type*) const' member function
declared in class 'std::locale'
int
On 12/20/2016 01:52 PM, Aldy Hernandez wrote:
int array[10] = { array[3]=5, 0x111, 0x222, 0x333 };
(gdb) x/4x
0x601040 : 0x0005 0x0111 0x0222
0x0005
That is, the array[3]=5 overwrites the last 0x333. I would expect that...
That may be wrong. Using the 4431
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78872
Bug ID: 78872
Summary: g++ refuses const trailing a function declaration.
Product: gcc
Version: 6.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
On Dec 20, 2016, at 6:10 AM, Dominik Vogt wrote:
> Right, it gets called even more often than one would think, and
> even with empty torture_current_options. The attached new patch
> (v3) removes -Ox options and superflous whitespace and caches that
> between calls if
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78516
--- Comment #18 from Peter Bergner ---
With the patch Vlad attached minus the one unwanted line/typo, I'm getting an
ICE on a powerpc64le-linux bootstrap. Looking into it.
/home/bergner/gcc/gcc-fsf-mainline-pr78516/libgcc/libgcc2.c: In
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70568
Michael Meissner changed:
What|Removed |Added
Known to work||4.8.5
Known to fail|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78823
Michael Meissner changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70568
--- Comment #6 from Michael Meissner ---
*** Bug 78823 has been marked as a duplicate of this bug. ***
Hi!
If the shift count has enough known zero low bits (non-zero bits only
above the ceil_log2 (precision)), then the only valid shift count that
is not out of bounds is 0, so we can as well fold it into the first
argument of the shift. This resolves a regression introduced by partly
optimizing
Hi!
DECL_ANON_UNION_VAR_P vars are DECL_ARTIFICIAL, but we still to diagnose
them if they shadow something. The DECL_ARTIFICIAL (x) check has been
missing in older gcc releases, so we diagnosed that properly.
Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
2016-12-20
Hi!
Similarly how we deal with bootstrapping libsanitizer only when
doing bootstrap-{a,u}san bootstrap, this avoids bootstrapping libmpx
if we don't need it for bootstrapping.
Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
2016-12-20 Jakub Jelinek
Hi!
Recently DW_FORM_ref_sup (which is meant e.g. for dwz, gcc doesn't emit it)
has been renamed to DW_FORM_ref_sup4 (and changed so that it is always 4
byte) and DW_FORM_ref_sup8 (always 8 byte) has been added.
Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
2016-12-20
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77767
--- Comment #7 from Jakub Jelinek ---
Unfortunately that version breaks the pr49120.c testcase, because mark_exp_read
doesn't deal with STATEMENT_LISTs. I'll test the other patch.
On 12/20/2016 11:48 AM, Nathan Sidwell wrote:
On 12/20/2016 11:25 AM, Aldy Hernandez wrote:
The problem in this PR is that we're trying to initialize an array with
members of itself:
Jakub has even gone further to show that for the following:
... = { array[3]=5, array[7]=3, array[7]=8,
On 12/20/16 16:09, Wilco Dijkstra wrote:
> Bernd Edlinger wrote:
>> this splits the *arm_negdi2, *arm_cmpdi_insn and *arm_cmpdi_unsigned
>> also at split1 except for TARGET_NEON and TARGET_IWMMXT.
>>
>> In the new test case the stack is reduced to about 270 bytes, except
>> for neon and iwmmxt,
On Tue, Dec 20, 2016 at 11:26:02AM -0600, Pat Haugen wrote:
> gcc.dg/sms-3.c and gcc.dg/sms-6.c fail on powerpc when -fsched-pressure is
> used. The -fsched-pressure option changes the value returned by
> rs6000_issue_rate which in turn affects the computed initiation interval in
> the SMS code
On December 20, 2016 4:50:25 PM GMT+01:00, Jeff Law wrote:
>On 12/20/2016 07:16 AM, Richard Biener wrote:
>>
>> it should be already set as we use visited_ssa as "was it ever on the
>worklist",
>> so maybe renaming it would be a good thing as well.
>>
>> + if
On December 20, 2016 5:01:19 PM GMT+01:00, Kyrill Tkachov
wrote:
>Hi all,
>
>The testcase in this patch generates bogus assembly for arm with -O1
>-mfloat-abi=soft:
>strdr4, [#0, r3]
>
>This is due to non-canonical RTL being generated during expansion:
This patch attempts to fix problems with the first scheduling pass creating too
much register pressure. It does this by enabling the target hook to compute the
pressure classes for rs6000 target since the first thing I observed while
investigating the testcase in the subject PR is that IRA was
gcc.dg/sms-3.c and gcc.dg/sms-6.c fail on powerpc when -fsched-pressure is
used. The -fsched-pressure option changes the value returned by
rs6000_issue_rate which in turn affects the computed initiation interval in the
SMS code and leads to failure to modulo schedule the single loop in sms-3.c
On Tue, 20 Dec 2016, Richard Biener wrote:
> Just noticed a few issues when feeding the GIMPLE FE random -gimple
> dumps. On errors not skipping to expected tokens leads to a load
> of strange followup parsing errors and worse, to endless parsing
> attempts in one case.
>
> Fixed with the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77754
--- Comment #8 from joseph at codesourcery dot com ---
On Tue, 20 Dec 2016, jakub at gcc dot gnu.org wrote:
> So, where would be the best place to remove the VLA bounds from parameters of
> fn declarations? Some function called from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77767
--- Comment #6 from joseph at codesourcery dot com ---
I think the append_to_statement_list version should be preferred.
On 12/20/2016 11:25 AM, Aldy Hernandez wrote:
The problem in this PR is that we're trying to initialize an array with
members of itself:
Jakub has even gone further to show that for the following:
... = { array[3]=5, array[7]=3, array[7]=8, array[7] = 9 };
things get even worse, because
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78871
Martin Liška changed:
What|Removed |Added
Keywords||ice-on-valid-code
On 12/12/16 09:04, Christophe Lyon wrote:
>>
>
> The new test (gcc.target/arm/pr78255-2.c scan-assembler b\\s+bar)
> added at r243494 fails on old arm architectures, such as:
> * arm-none-linux-gnueabi, forcing -march=armv5t in runtestflags
> * arm-none-eabi with default cpu/fpu/mode
>
>
The problem in this PR is that we're trying to initialize an array with
members of itself:
int array[10] = { array[3]=5, array[7]=3 };
The C++ front-end, in store_init_value() via cxx_constant_value() and
friends will transform:
{array[3] = 5, array[7] = 3}
into:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78516
--- Comment #17 from joseph at codesourcery dot com ---
On Tue, 20 Dec 2016, bergner at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78516
>
> --- Comment #16 from Peter Bergner ---
> (In reply to Vladimir Makarov
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78871
Bug ID: 78871
Summary: Anonymous namespace and -flto -gsplit-dwarf: ICE in
lhd_decl_printable_name, at langhooks.c:215
Product: gcc
Version: 7.0
Status: UNCONFIRMED
On Tue, Dec 20, 2016 at 05:04:54PM +0100, Andre Vehreschild wrote:
> Well, then how about:
>
> #define gfc_size_t_zero_node build_int_cst (size_type_node, 0)
>
> We can't get any faster and for new and old gfortran-hackers one identifier's
> meaning is faster to grasp than two's.
Such macros
Hi Janus,
> 1) After adding that code block in gfc_trans_assignment_1, it seems
> like the comment above is outdated, right?
Thanks for noting.
> 2) Wouldn't it be better to move this block, which does the correct
> allocation for CLASS variables, into
>
On 12/20/2016 05:14 AM, James Greenhalgh wrote:
On Tue, Dec 20, 2016 at 11:48:26AM +0100, Richard Biener wrote:
On Mon, Dec 19, 2016 at 6:58 PM, James Greenhalgh
wrote:
On Thu, Dec 8, 2016 at 10:44 PM, Uros Bizjak wrote:
Hello!
Attached patch
On Tue, 20 Dec 2016 16:40:13 +0100
Jakub Jelinek wrote:
> On Tue, Dec 20, 2016 at 04:29:07PM +0100, Andre Vehreschild wrote:
> > > The first one is GCC internal type for representing sizes, the latter is
> > > the C size_t (usually they have the same precision, they always
Hi all,
The testcase in this patch generates bogus assembly for arm with -O1
-mfloat-abi=soft:
strdr4, [#0, r3]
This is due to non-canonical RTL being generated during expansion:
(set (mem:DI (plus:SI (const_int 0 [0])
(reg/f:SI 153)) [0 MEM[symbol: a, index: _26,
On 12/20/2016 07:16 AM, Richard Biener wrote:
it should be already set as we use visited_ssa as "was it ever on the worklist",
so maybe renaming it would be a good thing as well.
+ if (TREE_CODE (name) == SSA_NAME)
+ {
+ /* If an SSA has already been
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78808
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78839
--- Comment #10 from Tom O'Connor ---
In regards to GDB, I noticed that when using a macro to get the offset for
these bitfields, with objects built by both GCC 5 and earlier as well as GCC 6,
I always get 0. For example:
(gdb) macro define
On Tue, Dec 20, 2016 at 04:29:07PM +0100, Andre Vehreschild wrote:
> > The first one is GCC internal type for representing sizes, the latter is
> > the C size_t (usually they have the same precision, they always have the
> > same signedness (unsigned)).
> > In the past sizetype actually has been a
On Tue, 20 Dec 2016 16:00:19 +0100
Jakub Jelinek wrote:
> On Tue, Dec 20, 2016 at 04:55:29PM +0200, Janne Blomqvist wrote:
> > On Tue, Dec 20, 2016 at 3:42 PM, Andre Vehreschild wrote:
> > > Hi all,
> > >
> > >> I think you should use
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72764
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78751
--- Comment #3 from Segher Boessenkool ---
Created attachment 40383
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40383=edit
patch
I use this patch as workaround. It, well, sucks. But it does work.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78660
--- Comment #5 from Paul Hua ---
(In reply to Paul Hua from comment #4)
>
> Maybe the r242326 cause the bug, the r242324 build success.
>
The r242326 and r242324 has another bug that r242522 fixed. If use r242326 to
reproduce this bug, you
Bernd Edlinger wrote:
> this splits the *arm_negdi2, *arm_cmpdi_insn and *arm_cmpdi_unsigned
> also at split1 except for TARGET_NEON and TARGET_IWMMXT.
>
> In the new test case the stack is reduced to about 270 bytes, except
> for neon and iwmmxt, where this does not change anything.
This looks
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71563
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
On Tue, Dec 20, 2016 at 04:55:29PM +0200, Janne Blomqvist wrote:
> On Tue, Dec 20, 2016 at 3:42 PM, Andre Vehreschild wrote:
> > Hi all,
> >
> >> I think you should use build_zero_cst(size_type_node) instead of
> >> size_zero_node as size_zero_node is of type sizetype which is not
Thought I gave an 'ok', but apparently never sent email.
Sorry about that. Yes, ok to commit.
--
steve
On Tue, Dec 20, 2016 at 04:56:51PM +0200, Janne Blomqvist wrote:
> PING!
>
> On Tue, Dec 13, 2016 at 10:59 PM, Janne Blomqvist
> wrote:
> > Use the
PING!
On Tue, Dec 13, 2016 at 10:59 PM, Janne Blomqvist
wrote:
> Use the boolean_type_node setup by the middle-end instead of
> redefining it. boolean_type_node is not used in GFortran for any
> ABI-visible stuff, only internally as the type of boolean
> expressions.
On Tue, Dec 20, 2016 at 3:42 PM, Andre Vehreschild wrote:
> Hi all,
>
>> I think you should use build_zero_cst(size_type_node) instead of
>> size_zero_node as size_zero_node is of type sizetype which is not the
>> same as size_type_node. Otherwise looks good.
>
> In the software
On 12/20/2016 11:06 AM, Martin Jambor wrote:
> ...this test should be for ADDR_EXPR here. Or you could switch the
> IPA_REF_* constants the other way round which I bet is going to have
> the same effect in practice, but personally, I'd test for ADDR_EXPR.
Thanks for the note, fixed (and tested
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78861
--- Comment #6 from mgansser at alice dot de
---
(In reply to Markus Trippelsdorf from comment #5)
> (In reply to Jonathan Wakely from comment #4)
> > No, that will convert the stream to a bool then try to bitshift it.
> >
> > It should be:
>
2016-11-26 0:28 GMT+03:00 Ilya Enkovich :
> 2016-11-25 15:47 GMT+03:00 Alexander Ivchenko :
>> Hi,
>>
>> The patch below addresses PR68270. could you please take a look?
>>
>> 2016-11-25 Alexander Ivchenko
>>
>>*
Hi,
On 19/12/16 21:43, Jeff Law wrote:
> On 12/19/2016 08:44 AM, James Cowgill wrote:
>> 2016-12-16 James Cowgill
>>
>> PR rtl-optimization/65618
>> * emit-rtl.c (try_split): Update "after" when moving a
>> NOTE_INSN_CALL_ARG_LOCATION.
>>
>> diff --git
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71724
Bernd Schmidt changed:
What|Removed |Added
CC||bernds at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78861
--- Comment #5 from Markus Trippelsdorf ---
(In reply to Jonathan Wakely from comment #4)
> No, that will convert the stream to a bool then try to bitshift it.
>
> It should be:
>
>result = bool( iss >> t.duration >> t.width );
Yeah,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78861
--- Comment #4 from Jonathan Wakely ---
No, that will convert the stream to a bool then try to bitshift it.
It should be:
result = bool( iss >> t.duration >> t.width );
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78863
--- Comment #3 from Martin Liška ---
Created attachment 40381
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40381=edit
Untested patch
On Fri, Dec 16, 2016 at 3:41 PM, Aldy Hernandez wrote:
> Hi folks.
>
> This is a follow-up on Jeff and Richi's interaction on the aforementioned PR
> here:
>
> https://gcc.gnu.org/ml/gcc-patches/2016-08/msg01397.html
>
> I decided to explore the idea of analyzing
Hello,
I am using BIT Fields in my program with powerPC target and when I am trying
check stack usage I see some strange values for the stack pointer.
typedef struct sample_type{
unsigned int var1 : 2;
unsigned int var2 : 2;
unsigned int var3 : 2;
unsigned int var4 : 2;
unsigned int var5 : 2;
On Tue, Dec 20, 2016 at 11:32:58AM +0100, Jakub Jelinek wrote:
> On Tue, Dec 20, 2016 at 11:22:47AM +0100, Dominik Vogt wrote:
> > On Mon, Dec 19, 2016 at 06:00:21PM +0100, Jakub Jelinek wrote:
> > > On Mon, Dec 19, 2016 at 05:50:40PM +0100, Dominik Vogt wrote:
> > > > *
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78861
--- Comment #3 from Markus Trippelsdorf ---
(In reply to mgans...@alice.de from comment #2)
> (In reply to Markus Trippelsdorf from comment #1)
> > https://gcc.gnu.org/gcc-6/porting_to.html
>
> I am not a software developer, could you please
On 20/12/16 13:26, Ulrich Weigand wrote:
> Torvald Riegel wrote:
>> On Fri, 2016-12-02 at 12:13 +0100, Gabriel Paubert wrote:
>>> On Thu, Dec 01, 2016 at 11:13:37AM -0800, Bin Fan at Work wrote:
Thanks for the comment. Yes, the ABI requires libatomic must query the
hardware. This is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78861
--- Comment #2 from mgansser at alice dot de
---
(In reply to Markus Trippelsdorf from comment #1)
> https://gcc.gnu.org/gcc-6/porting_to.html
I am not a software developer, could you please tell me, where can i get help ?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72707
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
Hi all,
> I think you should use build_zero_cst(size_type_node) instead of
> size_zero_node as size_zero_node is of type sizetype which is not the
> same as size_type_node. Otherwise looks good.
In the software design classes I took this was called a design error: Not
choosing sufficiently
> On Dec 19, 2016, at 6:04 PM, Bernd Schmidt wrote:
>
> I'll consider myself agnostic as to whether this is a feature we want or need,
Hi Bernd, thanks for reviewing this!
Regarding the usefulness of this feature, it has been discussed here (2 years
ago):
Torvald Riegel wrote:
> On Fri, 2016-12-02 at 12:13 +0100, Gabriel Paubert wrote:
> > On Thu, Dec 01, 2016 at 11:13:37AM -0800, Bin Fan at Work wrote:
> > > Thanks for the comment. Yes, the ABI requires libatomic must query the
> > > hardware. This is
> > > necessary if we want the compiler to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71827
--- Comment #5 from Jakub Jelinek ---
__INTPTR_TYPE__
foo ()
{
m: n: constexpr __INTPTR_TYPE__ a = ((__INTPTR_TYPE__) & -
(__INTPTR_TYPE__) &) + 23;
return a;
}
compiles fine, so it is considered an integral constant expression that just
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78660
--- Comment #4 from Paul Hua ---
The r243817 still build failure.
configure:3460: /home/xuchenghua/GCC/test/gcc-r243817_obj/./gcc/xgcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78847
--- Comment #5 from Richard Biener ---
Actually disabling reassoc is enough to "fix" it, the patch itself is not
needed,
fixed by VRP then (which also folds stmts and knows the trick).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71821
--- Comment #3 from Jakub Jelinek ---
TEMPLATE_ID_EXPR is considered to be potential_constant_expression_1, so
require_potential_rvalue_constant_expression (e)
at the start of cxx_alignas_expr. But cxx_eval_constant_expression does not
handle
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78839
Pierre-Marie de Rodat changed:
What|Removed |Added
CC||derodat at adacore dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78840
--- Comment #2 from Nathan Sidwell ---
Created attachment 40379
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40379=edit
reduced testcase.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78842
--- Comment #4 from Nathan Sidwell ---
sigh, bugzilla's moving on to 'random' other bug gets me. Again.
1 - 100 of 158 matches
Mail list logo