https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59859
Bug 59859 depends on bug 93134, which changed state.
Bug 93134 Summary: [graphite] ICE: Segmentation fault in ISL
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93134
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93134
Richard Biener changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
Hi!
Joseph reported ia32 glibc build ICEs, because the
*adddi3_doubleword_cc_overflow_1 pattern allows a memory output and matching
input, but addcarry* to which it splits doesn't, for some strange
reason it only allows register output. As it emits an adc instruction
which is very similar to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93132
--- Comment #2 from Pekka S ---
As the patch is pretty trivial, I think it's easiest if you simply make the
appropriate changes, including incrementing the atoi() values. I did mention
in the last paragraph that not incrementing the 1-based
On Tue, 7 Jan 2020, Andre Vieira (lists) wrote:
> Hello,
>
> Should we try to get this refactoring in stage 3 or park it for next stage 1?
I only looked at the patch now and I think it nicely simplifies things.
The patch is OK now with the usual function comment added before
}
+inline tree
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81806
Raihat Zaman Neloy changed:
What|Removed |Added
CC||raihatneloy1992 at gmail dot
com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93195
Bug ID: 93195
Summary: -fpatchable-function-entries :
__patchable_function_entries should consider comdat
groups
Product: gcc
Version: 10.0
Status:
On 2020/1/7 23:40, Jan Hubicka wrote:
>>
>>
>> On 2020/1/7 16:40, Jan Hubicka wrote:
On Mon, 2020-01-06 at 01:03 -0600, Xiong Hu Luo wrote:
> Inline should return failure either (newsize > param_large_function_insns)
> OR (newsize > limit). Sometimes newsize is larger than
>
Am 02.01.20 um 23:35 schrieb Thomas Koenig:
Hello world,
the attached patch fixes an ICE where an array constructor
containing an empty array constructor with a type didn't
get the type from the inner constructor.
The solution is to stash the type away in yet another variable
and only use it
On 1/6/20 4:17 PM, Jonathan Wakely wrote:
On 07/11/19 20:28 +0100, François Dumont wrote:
From what I understood from recent fix the unordered containers need
to be updated the same way.
I hope you'll appreciate the usage of rvalue forwarding. Containers
Yes, I think it makes sense.
node
Sorry, here is the patch.
--
Sender:bin.cheng
Sent At:2020 Jan. 8 (Wed.) 12:58
Recipient:GCC Patches
Subject:[PATCH GCC11]Improve uninitialized warning with value range info
Hi,
Function use_pred_not_overlap_with_undef_path_pred
Hi,
Function use_pred_not_overlap_with_undef_path_pred of
pass_late_warn_uninitialized
checks if predicate of variable use overlaps with predicate of undefined
control flow path.
For now, it only checks ssa_var comparing against constant, this can be
improved where
ssa_var compares against
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93194
--- Comment #1 from Fangrui Song ---
The SHF_WRITE issue has been fixed.
https://gcc.gnu.org/ml/gcc-patches/2020-01/msg00271.html will fix sh_addralign
Fixes https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93194
>From 60f489f2bf2b32afd1bdbb2405bb028dcedf82cc Mon Sep 17 00:00:00 2001
From: Fangrui Song
Date: Tue, 7 Jan 2020 20:46:26 -0800
Subject: [PATCH] Align __patchable_function_entries to POINTER_SIZE
To: gcc-patches@gcc.gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93177
--- Comment #1 from Andrew Pinski ---
ppu_intrinsics.h is installed for all powerpc* configs. Though to use it you
need to compile with -mcpu=cell :)
Tested x86_64-pc-linux-gnu, committed to trunk.
Jonathan Wakely writes:
> On 10/12/19 22:38 -0800, Thomas Rodgers wrote:
>>User-agent: mu4e 1.3.4; emacs 26.2
>> * include/std/condition_variable
>> (condition_variable_any::wait_on(_Lock&, stop_token, _Predicate): Rename
>> to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93084
--- Comment #13 from fxue at gcc dot gnu.org ---
Author: fxue
Date: Wed Jan 8 02:55:00 2020
New Revision: 279987
URL: https://gcc.gnu.org/viewcvs?rev=279987=gcc=rev
Log:
Find matched aggregate lattice for self-recursive CP (PR ipa/93084)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93194
Bug ID: 93194
Summary: -fpatchable-function-entries :
__patchable_function_entries has wrong sh_flags and
sh_addralign
Product: gcc
Version: unknown
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93189
--- Comment #3 from luoxhu at gcc dot gnu.org ---
Author: luoxhu
Revision: 279986
Modified property: svn:log
Modified: svn:log at Wed Jan 8 01:32:45 2020
--
--- svn:log
This Go frontend patch by Cherry Zhang fixes the loopdepth tracking in
array slicing expressions in escape analysis. In the gc compiler, for
slicing an array, its AST has an implicit address operation node.
There isn't such a node in the gofrontend AST. During escape
analysis, we create a fake
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93185
Frédéric Buclin changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
This patch to the Go frontend and libgo stops using
__go_runtime_error. We use specific panic functions instead, which
are mostly already in the runtime package. We also correct "defer
nil" to panic when we execute the defer, rather than throw when we
queue it. Bootstrapped and ran Go testsuite
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87256
--- Comment #12 from Sergei Trofimovich ---
I started looking at implementing full local cache in complement to global
evicting 'struct alg_hash_entry x_alg_hash[NUM_ALG_HASH_ENTRIES];' cache.
Noob question: which gcc's data structure should I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93193
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40752
Jason Merrill changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92124
--- Comment #4 from François Dumont ---
Author: fdumont
Date: Tue Jan 7 21:01:37 2020
New Revision: 279967
URL: https://gcc.gnu.org/viewcvs?rev=279967=gcc=rev
Log:
PR libstdc++/92124 fix incorrect container move assignment
*
> On Jan 7, 2020, at 7:43 AM, Jonathan Wakely wrote:
>
> For Jason and Krister's benefit, that last comment was referring to
> an earlier suggestion to not try to support old NetBSD releases, see
> https://gcc.gnu.org/ml/libstdc++/2020-01/msg00026.html
>
>> I think we need the netbsd target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93180
--- Comment #5 from pskocik at gmail dot com ---
Jakub Jelinek, I later asked how this worked on Stack Overflow
(https://stackoverflow.com/questions/59629946/why-do-gcc-and-clang-place-custom-sectioned-const-funcptr-symbols-into-writable).
Got no
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93193
Bug ID: 93193
Summary: C preprocessor works across commented lines
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93180
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93187
--- Comment #2 from Jakub Jelinek ---
Created attachment 47607
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47607=edit
gcc10-pr93187.patch
Untested fix.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93189
Andrew Pinski changed:
What|Removed |Added
Keywords||build
Component|testsuite
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93187
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
On Tue, Jan 7, 2020 at 7:58 AM Christophe Lyon
wrote:
>
> Hi,
>
> I've received a support request where GCC generates strd/ldrd which
> require aligned memory addresses, while the user code actually
> provides sub-aligned pointers.
>
> The sample code is derived from CMSIS:
> #define
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93192
--- Comment #1 from Andrew Pinski ---
Patches should be sent to gcc-patches@ after reading
https://gcc.gnu.org/contribute.html .
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47071
Andrew Pinski changed:
What|Removed |Added
CC||ian.s.mcinerney at ieee dot org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93190
Andrew Pinski changed:
What|Removed |Added
Resolution|INVALID |DUPLICATE
--- Comment #7 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93192
Bug ID: 93192
Summary: [m68k] incorrect conversion of inf and nan in
__truncxfdf2
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67202
Thomas Koenig changed:
What|Removed |Added
Host|67202 |
--- Comment #4 from Thomas Koenig ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93190
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93190
--- Comment #5 from Ian McInerney ---
Created attachment 47605
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47605=edit
Verbose output from successful linking
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93190
--- Comment #4 from Ian McInerney ---
Created attachment 47604
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47604=edit
GCC verbose output from failed linking
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93191
Bug ID: 93191
Summary: Conversions to arrays of unknown bound P0388 Fails for
variadic args
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93190
--- Comment #3 from Ian McInerney ---
Note that I am compiling this with
g++ -fno-lto -v -Wl,-v main.cpp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93190
--- Comment #2 from Ian McInerney ---
Created attachment 47603
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47603=edit
Object file from successful linking
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93190
--- Comment #1 from Ian McInerney ---
Created attachment 47602
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47602=edit
Object file from failed linking
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93190
Bug ID: 93190
Summary: Failure to link with .note.GNU-stack in inline
assembly
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93132
Martin Sebor changed:
What|Removed |Added
Keywords||diagnostic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93189
--- Comment #2 from seurer at gcc dot gnu.org ---
And prevents 176.gcc in spec2000 from building
c-lex.o: In function `init_lex':
c-lex.c:(.text+0xb30): undefined reference to `is_reserved_word'
c-lex.c:(.text+0xc68): undefined reference to
Hi!
On 2020-01-07T08:20:44+0100, Jakub Jelinek wrote:
> When I wrote the code, for map clause the arguments couldn't contain any
> REF_COMPONENT (nor REF_UNQUIRY nor REF_SUBSTRING) and therefore it was
> ok (although unclean) to just look at u.ar.type
Jakub, thanks for fixing this.
> but now
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91364
--- Comment #10 from Marek Polacek ---
(In reply to Will Wray from comment #7)
> Fails to match for variadic arguments. Reopen or file a new bug?
Definitely a new bug, please.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93189
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #1
Olivier Hainque writes:
> Hi Andrew,
>
>> On 6 Jan 2020, at 23:24, Andrew Pinski wrote:
>> Just one small suggestion:
>
> Sure
>
>> Instead of:
>> - char* pStr = alloca(SIZE);
>> + char* pStr = __builtin_alloca(SIZE);
>>
>> Why not just do:
>> -#include
>> +#define alloca __builtin_alloca
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93174
--- Comment #3 from Jakub Jelinek ---
Created attachment 47600
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47600=edit
gcc10-pr93174.patch
Untested fix.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91364
--- Comment #9 from Will Wray ---
The variadic unknown-bound 1st overload matches exact T(&)[] only
https://godbolt.org/z/9qZpWX
#include
void cat(auto const(&...cstr)[]) { (((void)cstr,puts("G'bye")),...); }
void cat(auto const(&...cstr)[6])
Thanks for the update. The new patch looks really good, just some
minor comments.
Stam Markianos-Wright writes:
> [...]
> Also I've update the filenames of all our tests to make them a bit clearer:
>
> C tests:
>
> __ bfloat16_scalar_compile_1.c to bfloat16_scalar_compile_3.c: Compilation of
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93189
Bug ID: 93189
Summary: [10 regression] Many test case failures starting with
r279942
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91364
--- Comment #8 from Will Wray ---
Reduced example (but still with puts output) https://godbolt.org/z/Ttc2Za
#include
void cat(auto const(&...cstr)[]) { (puts(cstr),...); }
// Comment out this next line[6]
void cat(auto
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93174
Jakub Jelinek changed:
What|Removed |Added
Priority|P3 |P1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89096
james north changed:
What|Removed |Added
CC||douglas_north at hotmail dot
com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91364
Will Wray changed:
What|Removed |Added
CC||wjwray at gmail dot com
--- Comment #7 from
CannaWest
http://links.infocastevents.mkt8115.com/ctt?kn=13=NDE0ODk2MDMS1=NjkyMTk1NzM3MTk0S0=2=MTY4MDY1Nzc0NwS2=1=0
The
On Tue, 7 Jan 2020 at 17:18, Marc Glisse wrote:
>
> On Tue, 7 Jan 2020, Christophe Lyon wrote:
>
> > I've received a support request where GCC generates strd/ldrd which
> > require aligned memory addresses, while the user code actually
> > provides sub-aligned pointers.
> >
> > The sample code is
On Tue, 7 Jan 2020 at 17:06, Richard Earnshaw (lists)
wrote:
>
> On 07/01/2020 15:57, Christophe Lyon wrote:
> > Hi,
> >
> > I've received a support request where GCC generates strd/ldrd which
> > require aligned memory addresses, while the user code actually
> > provides sub-aligned pointers.
>
> On 1/7/20 11:08 AM, Jan Hubicka wrote:
> > > On 1/6/20 8:03 PM, Jan Hubicka wrote:
> > > > > > > OK
> > > > > > Actually I am not so sure about this patch - how do we ensure
> > > > > > reproducibility in this case?
> > > > > ISTM that anyone trying to have reproducible builds shouldn't be using
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93184
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
CC||rsandifo at gcc dot
On Tue, 7 Jan 2020, Christophe Lyon wrote:
I've received a support request where GCC generates strd/ldrd which
require aligned memory addresses, while the user code actually
provides sub-aligned pointers.
The sample code is derived from CMSIS:
#define __SIMD32_TYPE int
#define __SIMD32(addr)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93183
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93188
Richard Earnshaw changed:
What|Removed |Added
Target||arm
Status|UNCONFIRMED
On 07/01/2020 15:57, Christophe Lyon wrote:
Hi,
I've received a support request where GCC generates strd/ldrd which
require aligned memory addresses, while the user code actually
provides sub-aligned pointers.
The sample code is derived from CMSIS:
#define __SIMD32_TYPE int
#define
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93188
Bug ID: 93188
Summary: a-profile multilib mismatch for rmprofile toolchain
when architecture includes +mp or +sec
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Hi,
I've received a support request where GCC generates strd/ldrd which
require aligned memory addresses, while the user code actually
provides sub-aligned pointers.
The sample code is derived from CMSIS:
#define __SIMD32_TYPE int
#define __SIMD32(addr) (*(__SIMD32_TYPE **) & (addr))
void
Richard,
Thanks for the offer, but no need. Just wanted to confirm with some
detail that I reviewed aspects of the svn-git conversion and LGTM.
BTW, I too saw the issue (in 14 out of 261 master commits) reported by
Andrew where (in my case) "ljrit...@gcc.gnu.org" was used in Author
line(s)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93187
Bug ID: 93187
Summary: [10 Regression] ICE in extract_insn, at recog.c:2294
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93174
Joseph S. Myers changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
Target
> On Tue, Jan 7, 2020 at 3:26 PM Jan Hubicka wrote:
> >
> > > Err - Optimization also lists it in some -help section? It's a Warning
> > > option and certainly we don't handle per-function Warnings in general
> > > (with LTO) even though we have #pragma GCC diagnostic, no?
> > >
> > > I'm not
On 07/01/20 15:40 +, Jonathan Wakely wrote:
On 07/01/20 01:30 +0100, Kamil Rytarowski wrote:
On 07.01.2020 01:26, Jonathan Wakely wrote:
On 06/01/20 23:20 +0100, Kamil Rytarowski wrote:
On 06.01.2020 16:24, Jonathan Wakely wrote:
On 22/12/19 09:36 +1000, Gerald Pfeifer wrote:
Hi
Andi Kleen writes:
Ping!
> Andi Kleen writes:
>
> Ping!
>
>> Andi Kleen writes:
>>
>> Ping!
>>
>>> Andi Kleen writes:
>>>
>>> Ping!
>>>
Andi Kleen writes:
Ping!
> From: Andi Kleen
>
> [v4: Rebased on current tree. Avoid some redundant log statements
>
>
>
> On 2020/1/7 16:40, Jan Hubicka wrote:
> >> On Mon, 2020-01-06 at 01:03 -0600, Xiong Hu Luo wrote:
> >>> Inline should return failure either (newsize > param_large_function_insns)
> >>> OR (newsize > limit). Sometimes newsize is larger than
> >>> param_large_function_insns, but smaller
On 07/01/20 01:30 +0100, Kamil Rytarowski wrote:
On 07.01.2020 01:26, Jonathan Wakely wrote:
On 06/01/20 23:20 +0100, Kamil Rytarowski wrote:
On 06.01.2020 16:24, Jonathan Wakely wrote:
On 22/12/19 09:36 +1000, Gerald Pfeifer wrote:
Hi Matthew,
On Mon, 4 Feb 2019, Matthew Bauer wrote:
The
This patch to the Go frontend avoids generating a write barrier for
code that appears in the Go1.14beta1 runtime package in
(*pageAlloc).sysGrow:
s.summary[l] = s.summary[l][:needIdxLimit]
Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu. Committed
to mainline.
Ian
Index:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93186
Bug ID: 93186
Summary: C++ compile time hog
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee:
Hi Andrew,
> On 6 Jan 2020, at 23:24, Andrew Pinski wrote:
> Just one small suggestion:
Sure
> Instead of:
> - char* pStr = alloca(SIZE);
> + char* pStr = __builtin_alloca(SIZE);
>
> Why not just do:
> -#include
> +#define alloca __builtin_alloca
Yes, good idea.
Revised patch attached,
This patch add vector comparison patterns for many more modes.
These test failures now pass:
FAIL: gcc.dg/vect/pr65947-2.c scan-tree-dump-times vect "LOOP VECTORIZED" 2
FAIL: gcc.dg/vect/pr65947-5.c scan-tree-dump-times vect "LOOP VECTORIZED" 2
FAIL: gcc.dg/vect/pr65947-9.c scan-tree-dump-times
Stam Markianos-Wright writes:
> On 12/19/19 10:08 AM, Richard Sandiford wrote:
>> Stam Markianos-Wright writes:
>>> diff --git a/gcc/config/aarch64/aarch64.c b/gcc/config/aarch64/aarch64.c
>>> index f57469b6e23..f40f6432fd4 100644
>>> --- a/gcc/config/aarch64/aarch64.c
>>> +++
Hi,
>On 1/6/20 7:10 AM, Jonathan Wakely wrote:
>> GCC now defaults to -fno-common. As a result, global
>> variable accesses are more efficient on various targets. In C, global
>> variables with multiple tentative definitions will result in linker
>> errors.
>
> This is better. I'd also
On 12/12/19 4:18 PM, Matthew Malcomson wrote:
Hello.
I've just sent few comments that are related to the v3 of the patch set.
Based on the HWASAN (limited) knowledge the patch seems reasonable to me.
I haven't looked much at the newly introduced RTL-hooks.
But these seems to me isolated to the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55791
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
--- Comment #5
On 12/12/19 4:19 PM, Matthew Malcomson wrote:
- if (is_store && !param_asan_instrument_writes)
+ if (is_store
+ && (!param_asan_instrument_writes || !param_hwasan_instrument_writes))
return;
- if (!is_store && !param_asan_instrument_reads)
+ if (!is_store
+ && (!param_asan_instrument_reads ||
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47877
Jason Merrill changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47877
--- Comment #6 from Jason Merrill ---
Author: jason
Date: Tue Jan 7 15:05:25 2020
New Revision: 279960
URL: https://gcc.gnu.org/viewcvs?rev=279960=gcc=rev
Log:
PR c++/47877 - -fvisibility-inlines-hidden and member templates.
On 1/7/20 5:46 AM, Paolo Carlini wrote:
Hi,
On 06/01/20 21:47, Jason Merrill wrote:
On 1/2/20 4:23 AM, Paolo Carlini wrote:
@@ -19320,8 +19320,8 @@ tsubst_copy_and_build (tree t,
tree op1 = tsubst (TREE_OPERAND (t, 1), args, complain,
in_decl);
tree op2 = RECUR (TREE_OPERAND
DECL_VISIBILITY_SPECIFIED is also true if an enclosing scope has explicit
visibility, and we don't want that to override -fvisibility-inlines-hidden.
So check for the attribute specifically on the function, like we already do
for template argument visibility restriction.
Tested
On 12/12/19 4:19 PM, Matthew Malcomson wrote:
+-param=hwasan-stack=
+Common Joined UInteger Var(param_hwasan_stack) Init(1) IntegerRange(0, 1) Param
+Enable hwasan stack protection.
+
+-param=hwasan-random-frame-tag=
+Common Joined UInteger Var(param_hwasan_random_frame_tag) Init(1)
This patch fixes some failures to assemble I encountered while fixing
other issues (not yet posted).
These were caused by emitting 'B' immediates that the ISA manual
indicates should work, but the assembler rejects. I've confirmed that
they are, in fact, not handled by the hardware; if I
On Tue, Jan 7, 2020 at 3:26 PM Jan Hubicka wrote:
>
> > Err - Optimization also lists it in some -help section? It's a Warning
> > option and certainly we don't handle per-function Warnings in general
> > (with LTO) even though we have #pragma GCC diagnostic, no?
> >
> > I'm not sure why we
在 2019/11/20 下午9:11, JunMa 写道:
在 2019/11/20 下午7:22, Iain Sandoe 写道:
Hello JunMa,
JunMa wrote:
在 2019/11/17 下午6:28, Iain Sandoe 写道:
I find that the patches donot support 'for co_await'. And it is
quiet simple to implement range based 'for co_await' based on your
patches, since it's just need
On Wed, Dec 18, 2019 at 10:59 AM Andrew Pinski wrote:
>
> On Wed, Dec 18, 2019 at 1:18 AM Hongtao Liu wrote:
> >
> > On Wed, Dec 18, 2019 at 4:26 PM Segher Boessenkool
> > wrote:
> > >
> > > On Wed, Dec 18, 2019 at 10:37:11AM +0800, Hongtao Liu wrote:
> > > > Hi:
> > > > This patch is to
> Err - Optimization also lists it in some -help section? It's a Warning
> option and certainly we don't handle per-function Warnings in general
> (with LTO) even though we have #pragma GCC diagnostic, no?
>
> I'm not sure why we force warn_inline to zero with -O0, it seems much
> better to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91525
--- Comment #3 from gcc-bugs at marehr dot dialup.fu-berlin.de ---
On gcc-10 I get now the following stacktrace:
```
g++-git -std=c++17 -fconcepts -c ice.cpp
main.cpp: In function ‘std::string e()’:
main.cpp:46:16: internal compiler error:
1 - 100 of 194 matches
Mail list logo