https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107890
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107937
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107935
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
On Thu, Dec 1, 2022 at 12:26 AM Segher Boessenkool
wrote:
>
> Hi!
>
> On Wed, Nov 30, 2022 at 03:16:25PM -0300, Adhemerval Zanella via Gcc-patches
> wrote:
> > clang by default rejects the input casts with:
> >
> > error: invalid use of a cast in a inline asm context requiring an
> > lvalue:
Hi Kewen,
在 12/1/22 2:11 PM, Kewen.Lin 写道:
> on 2022/12/1 13:35, Jiufu Guo wrote:
>> Hi Kewen,
>>
>> Thanks for your quick and insight review!
>>
>> 在 12/1/22 1:17 PM, Kewen.Lin 写道:
>>> Hi Jeff,
>>>
>>> on 2022/12/1 09:36, Jiufu Guo wrote:
Hi,
This patch just uses sext_hwi to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107409
--- Comment #9 from Rama Malladi ---
(In reply to Martin Liška from comment #3)
> Can you please share perf-profile before and after the revision?
>
> Note I can't see it for Altra aarch64 CPU:
>
Hi Kewen,
在 12/1/22 1:30 PM, Kewen.Lin 写道:
> on 2022/12/1 13:17, Kewen.Lin via Gcc-patches wrote:
>> Hi Jeff,
>>
>> on 2022/12/1 09:36, Jiufu Guo wrote:
>>> Hi,
>>>
>>> This patch just uses sext_hwi to replace the expression like:
>>> ((value & 0xf..f) ^ 0x80..0) - 0x80..0 for rs6000.cc and
;; if reg/mem op
(define_insn_reservation "slm_sseishft_3" 2
(and (eq_attr "cpu" "slm")
(and (eq_attr "type" "sseishft")
(not (match_operand 2 "immediate_operand"
"slm-complex, slm-all-eu")
in slm.md it will check operands[2] for type sseishft, but for
extendbfsf2_1
on 2022/12/1 13:35, Jiufu Guo wrote:
> Hi Kewen,
>
> Thanks for your quick and insight review!
>
> 在 12/1/22 1:17 PM, Kewen.Lin 写道:
>> Hi Jeff,
>>
>> on 2022/12/1 09:36, Jiufu Guo wrote:
>>> Hi,
>>>
>>> This patch just uses sext_hwi to replace the expression like:
>>> ((value & 0xf..f) ^
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107943
Bug ID: 107943
Summary: gcc -fanalyzer hangs in openssl curve25519.c
Product: gcc
Version: 12.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
Hi Kewen,
Thanks for your quick and insight review!
在 12/1/22 1:17 PM, Kewen.Lin 写道:
> Hi Jeff,
>
> on 2022/12/1 09:36, Jiufu Guo wrote:
>> Hi,
>>
>> This patch just uses sext_hwi to replace the expression like:
>> ((value & 0xf..f) ^ 0x80..0) - 0x80..0 for rs6000.cc and rs6000.md.
>>
>>
on 2022/12/1 13:17, Kewen.Lin via Gcc-patches wrote:
> Hi Jeff,
>
> on 2022/12/1 09:36, Jiufu Guo wrote:
>> Hi,
>>
>> This patch just uses sext_hwi to replace the expression like:
>> ((value & 0xf..f) ^ 0x80..0) - 0x80..0 for rs6000.cc and rs6000.md.
>>
>> Bootstrap & regtest pass on ppc64{,le}.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107937
--- Comment #6 from Martin Liška ---
Another test-case:
$ cat warn.i
int regs, vm_debug_engine_vp_0, vm_debug_engine_vp_2;
void
vm_dispatch_hook();
void
vm_debug_engine() {
int fp;
void *jump_table = &_nop;
l_nop:
if
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107937
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
Hi Jeff,
on 2022/12/1 09:36, Jiufu Guo wrote:
> Hi,
>
> This patch just uses sext_hwi to replace the expression like:
> ((value & 0xf..f) ^ 0x80..0) - 0x80..0 for rs6000.cc and rs6000.md.
>
> Bootstrap & regtest pass on ppc64{,le}.
> Is this ok for trunk?
You didn't say it clearly but I
Hi Kewen,
在 12/1/22 11:31 AM, Kewen.Lin 写道:
> Hi Jeff,
>
> on 2022/12/1 09:36, Jiufu Guo wrote:
>> Hi,
>>
>> Function rs6000_emit_set_const/rs6000_emit_set_long_const are only invoked
>> from
>> two "define_split"s where the target operand is limited to gpc_reg_operand or
>> int_reg_operand,
As implied in
gcc.gnu.org/legacy-ml/gcc-patches/2008-09/msg00076.html,
gcc provides -Wno-builtin-macro-redefined to suppress warning when
redefining builtin macro. However, at that time, there was no
scenario for __LINE__ macro.
But, when we try to build a live-patch, we compare sections by using
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=18333
--- Comment #7 from Hans-Peter Nilsson ---
Haha, wow. I just had to look... Yeah, definitely a proper WONTFIX.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27513
Andrew Pinski changed:
What|Removed |Added
Status|NEW |SUSPENDED
--- Comment #5 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=15532
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
Last
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26356
Andrew Pinski changed:
What|Removed |Added
CC||pinskia at gcc dot gnu.org
Tested x86_64-pc-linux-gnu, applying to trunk.
-- 8< --
The first is an actual bug: remove_contract_attributes was only keeping one
attribute. The second just helps flow analysis in optimizers and static
analyzers.
gcc/cp/ChangeLog:
* contracts.cc (remove_contract_attributes):
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107863
--- Comment #15 from Hongtao.liu ---
Fixed in GCC10.5, GCC11.4,GCC12.3 and GCC13.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107863
--- Comment #14 from CVS Commits ---
The releases/gcc-10 branch has been updated by hongtao Liu
:
https://gcc.gnu.org/g:ac30c91a1002ae4049a4773d07d5da41e7bd3138
commit r10-11105-gac30c91a1002ae4049a4773d07d5da41e7bd3138
Author: liuhongt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=16172
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107863
--- Comment #13 from CVS Commits ---
The releases/gcc-11 branch has been updated by hongtao Liu
:
https://gcc.gnu.org/g:e6d28f7fd4573988b2417a52acd0a27b7ee91681
commit r11-10404-ge6d28f7fd4573988b2417a52acd0a27b7ee91681
Author: liuhongt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107863
--- Comment #12 from CVS Commits ---
The releases/gcc-12 branch has been updated by hongtao Liu
:
https://gcc.gnu.org/g:b7306f02da33695bec90f153f6725a51d7c0ac71
commit r12-8954-gb7306f02da33695bec90f153f6725a51d7c0ac71
Author: liuhongt
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107863
--- Comment #11 from CVS Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:cda29c540037fbcf00a377196050953aab1d3d5b
commit r13-4432-gcda29c540037fbcf00a377196050953aab1d3d5b
Author: liuhongt
Date: Mon
Hi Jeff,
on 2022/12/1 09:36, Jiufu Guo wrote:
> Hi,
>
> Function rs6000_emit_set_const/rs6000_emit_set_long_const are only invoked
> from
> two "define_split"s where the target operand is limited to gpc_reg_operand or
> int_reg_operand, then the operand must be REG_P.
> And in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=18333
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98776
--- Comment #10 from Sebastian Pop ---
Patch for arm64:
https://gcc.gnu.org/pipermail/gcc-patches/2022-December/607601.html
On 2022-12-01 06:50 Palmer Dabbelt wrote:
>
>On Wed, 30 Nov 2022 00:37:17 PST (-0800), gao...@eswincomputing.com wrote:
>> The stack that save-restore reserves is not well accumulated in stack
>> allocation and deallocation.
>> This patch allows less instructions to be used in stack allocation
Hi,
Currently patchable area is at the wrong place on AArch64. It is placed
immediately after function label, before .cfi_startproc. This patch
adds UNSPECV_PATCHABLE_AREA for pseudo patchable area instruction and
modifies aarch64_print_patchable_function_entry to avoid placing
patchable area
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107928
David Malcolm changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to trunk as r13-4431-geaaf97b6147095.
gcc/analyzer/ChangeLog:
PR analyzer/106626
* bounds-checking.cc
(symbolic_past_the_end::describe_final_event): Delete, moving to
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to trunk as r13-4425-gb82b361af888a1.
gcc/ChangeLog:
* Makefile.in (ANALYZER_OBJS): Add analyzer/bounds-checking.o.
gcc/analyzer/ChangeLog:
* bounds-checking.cc: New file, taken from region-model.cc.
*
The region-creation event at the start of...
: In function 'int_arr_write_element_after_end_off_by_one':
:14:11: warning: buffer overflow [CWE-787] [-Wanalyzer-out-of-bounds]
14 | arr[10] = x;
| ^~~
event 1
|
| 10 | int32_t arr[10];
| | ^~~
|
This patch tweaks the wording of -Wanalyzer-out-of-bounds:
* use the spellings/terminology of CWE:
* replace "underread" with "under-read", as per:
https://cwe.mitre.org/data/definitions/127.html
* replace "overread" with "over-read" as per:
Convert out-of-bounds class hierarchy from:
pending_diagnostic
out_of_bounds
past_the_end
buffer_overflow (*)
buffer_over_read (*)
buffer_underwrite (*)
buffer_under_read (*)
symbolic_past_the_end
symbolic_buffer_overflow (*)
Consider -fanalyzer on:
#include
int32_t arr[10];
void int_arr_write_element_after_end_off_by_one(int32_t x)
{
arr[10] = x;
}
Trunk x86_64: https://godbolt.org/z/17zn3qYY4
Currently we emit:
: In function 'int_arr_write_element_after_end_off_by_one':
:7:11: warning: buffer overflow
Consider -fanalyzer on:
#include
int32_t arr[10];
void int_arr_write_element_after_end_far(int32_t x)
{
arr[100] = x;
}
Trunk x86_64: https://godbolt.org/z/7GqEcYGq6
Currently we emit:
: In function 'int_arr_write_element_after_end_far':
:7:12: warning: buffer overflow [CWE-787]
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to trunk as r13-4424-g45a75fd3d31265.
gcc/analyzer/ChangeLog:
PR analyzer/107928
* sm-fd.cc (fd_state_machine::on_bind): Handle m_constant_fd in
the "success" outcome.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106626
--- Comment #6 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:eaaf97b6147095cc19f7efdefaf55c8ebe7a94e8
commit r13-4431-geaaf97b6147095cc19f7efdefaf55c8ebe7a94e8
Author: David Malcolm
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106626
--- Comment #3 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:7c655699ed51b0c987e5472767db48b19044ae05
commit r13-4427-g7c655699ed51b0c987e5472767db48b19044ae05
Author: David Malcolm
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106626
--- Comment #5 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:1d86af242bc4a8e68aebf1f3b8c985f2d17fa791
commit r13-4429-g1d86af242bc4a8e68aebf1f3b8c985f2d17fa791
Author: David Malcolm
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106626
--- Comment #4 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:df460cf51b25868564dd2628a399b8c874ef309c
commit r13-4428-gdf460cf51b25868564dd2628a399b8c874ef309c
Author: David Malcolm
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106626
--- Comment #2 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:d69a95c12cc91ec10d6a8c78f401bf6720b08fce
commit r13-4426-gd69a95c12cc91ec10d6a8c78f401bf6720b08fce
Author: David Malcolm
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107928
--- Comment #3 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:45a75fd3d31265e43aa3ce7a5e851083d534b00b
commit r13-4424-g45a75fd3d31265e43aa3ce7a5e851083d534b00b
Author: David Malcolm
Date:
Date: Thu, 01 Dec 2022 09:51:32 +0800
In-Reply-To: <20221125144309.gg25...@gate.crashing.org> (Segher Boessenkool's
message of "Fri, 25 Nov 2022 08:43:09 -0600")
Message-ID: <7ewn7bx55n@pike.rch.stglabs.ibm.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux)
Segher
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106773
--- Comment #7 from James Hilliard ---
There's also this error during skeleton generation for kfunc_call_test.c:
$ /home/buildroot/bpf-next/tools/testing/selftests/bpf/tools/sbin/bpftool
--debug gen skeleton
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100866
--- Comment #16 from CVS Commits ---
The master branch has been updated by HaoChen Gui :
https://gcc.gnu.org/g:9d68cba5eb20442f8075b8f92d1b20a00022852f
commit r13-4423-g9d68cba5eb20442f8075b8f92d1b20a00022852f
Author: Haochen Gui
Date: Wed
Date: Thu, 01 Dec 2022 09:48:06 +0800
In-Reply-To: <20221128171950.gn25...@gate.crashing.org> (Segher Boessenkool's
message of "Mon, 28 Nov 2022 11:19:50 -0600")
Message-ID: <7e4jufyjvt@pike.rch.stglabs.ibm.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux)
Segher
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95067
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |WONTFIX
Target Milestone|10.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107934
--- Comment #3 from Hongtao.liu ---
(In reply to Uroš Bizjak from comment #2)
> The type of extendbfsf2_1 insn should be sseishft1.
Yes.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59447
Andrew Pinski changed:
What|Removed |Added
Assignee|pinskia at gcc dot gnu.org |unassigned at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31230
--- Comment #6 from Andrew Pinski ---
r0-101483-g5c9fae0d6eee58 removed the TYPE_SYMTAB_POINTER part of
type_hash_marked_p .
I have no idea if the rest still applies. Plus stabs debugging has been removed
in GCC 13.
Hi,
Function rs6000_emit_set_const/rs6000_emit_set_long_const are only invoked from
two "define_split"s where the target operand is limited to gpc_reg_operand or
int_reg_operand, then the operand must be REG_P.
And in rs6000_emit_set_const/rs6000_emit_set_long_const, to create temp rtx,
it is
Hi,
This patch just uses sext_hwi to replace the expression like:
((value & 0xf..f) ^ 0x80..0) - 0x80..0 for rs6000.cc and rs6000.md.
Bootstrap & regtest pass on ppc64{,le}.
Is this ok for trunk?
BR,
Jeff (Jiufu)
gcc/ChangeLog:
* config/rs6000/rs6000.cc (num_insns_constant_gpr): Use
Hi,
This patch is just using a more readable pattern for "rldicl x,x,0,32"
to clean high 32bits.
Old pattern looks like: r118:DI=zero_extend(r120:DI#0)
new pattern looks like: r118:DI=r120:DI&0x
Bootstrap and regtest pass on ppc64{,le}.
Is this ok for trunk?
BR,
Jeff (Jiufu)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46322
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31235
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71058
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47966
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=9161
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |WONTFIX
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=12869
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |WONTFIX
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56578
Andrew Pinski changed:
What|Removed |Added
Summary|Testcase behaves|Testcase behaves
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53998
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |WONTFIX
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107927
--- Comment #3 from Lars Gullik Bjønnes ---
I cannot send you the unreduced preprocessed code and I have failed at creating
a small
snippet that produces the error.
This is the compiler output though.
Something might be gleaned from that.
In
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93738
Michael Meissner changed:
What|Removed |Added
CC||meissner at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107942
--- Comment #6 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #5)
> Oh it is still part of the keyword index too:
> https://gcc.gnu.org/onlinedocs/gcc/Keyword-Index.html#Keyword-Index
>
> Which links to:
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107942
--- Comment #5 from Andrew Pinski ---
Oh it is still part of the keyword index too:
https://gcc.gnu.org/onlinedocs/gcc/Keyword-Index.html#Keyword-Index
Which links to:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106773
--- Comment #6 from James Hilliard ---
https://github.com/torvalds/linux/blob/v6.1-rc7/tools/testing/selftests/bpf/bpf_legacy.h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107942
--- Comment #4 from Andrew Pinski ---
Reference to the patch that was sent:
https://gcc.gnu.org/pipermail/gcc-patches/2015-March/414153.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107942
--- Comment #3 from Andrew Pinski ---
Here is the sample program to prove that const is still handled like const
attribute:
```
typedef int voidfn (void);
const voidfn constt;
[[gnu::noipa]]
int constt(void) {return 1;}
int f(void)
{
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106773
--- Comment #5 from James Hilliard ---
(In reply to David Faust from comment #4)
> Created attachment 53993 [details]
> proposed patch
>
> Should fix the remaining issues with 'extern' linkage and the missing
> 'const' modifier (and includes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46542
Bug 46542 depends on bug 46888, which changed state.
Bug 46888 Summary: missed optimization of zero_extract with constant inputs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46888
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46888
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107942
Andrew Pinski changed:
What|Removed |Added
Summary|[10/11/12/13 Regression]|[10/11/12/13 Regression]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107942
Andrew Pinski changed:
What|Removed |Added
Known to work||4.8.5
Known to fail|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107942
Bug ID: 107942
Summary: [10/11/12/13 Regression] Documentation of the volatile
style for noreturn is gone
Product: gcc
Version: 13.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99576
--- Comment #14 from Iain Sandoe ---
(In reply to Iain Sandoe from comment #13)
> (In reply to Adrian Perl from comment #12)
> > I have sent the patch and tests to gcc-patc...@gcc.gnu.org
>
> As noted there, the patch causes regressions in more
On Thu, Dec 01, 2022 at 12:17:30AM +0100, Andreas Schwab wrote:
> On Nov 30 2022, Segher Boessenkool wrote:
>
> > char u[1] = { "x", "x" }; /* { dg-error {excess elements in 'char[1]'
> > initializer} } */
>
> That won't work, as '[1]' is a bracket expression only matching '1'.
> You'll need
Hi!
On Wed, Nov 30, 2022 at 03:16:25PM -0300, Adhemerval Zanella via Gcc-patches
wrote:
> clang by default rejects the input casts with:
>
> error: invalid use of a cast in a inline asm context requiring an
> lvalue: remove the cast or build with -fheinous-gnu-extensions
>
> And even with
On Nov 30 2022, Segher Boessenkool wrote:
> char u[1] = { "x", "x" }; /* { dg-error {excess elements in 'char[1]'
> initializer} } */
That won't work, as '[1]' is a bracket expression only matching '1'.
You'll need {... 'char\[1\]' ...}.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96425
--- Comment #7 from Sergei Trofimovich ---
If I bisected correctly SIGSEGV disappeared in r11-2735-g634046d1a81b48
commit 634046d1a81b48a48b3564ff2f90974f6b7b087b
Author: Nathan Sidwell
Date: Tue Aug 18 06:02:37 2020 -0700
c++: Move
Hi!
On Wed, Nov 30, 2022 at 09:18:15AM -0800, apinski--- via Gcc-patches wrote:
> Note in the testsuite I used regex . to match '[' and ']' as
> I could not figure out how many '\' I needed.
Don't use double quotes then :-) Inside double quotes all of command
substitution, variable
On Wed, 30 Nov 2022 00:37:17 PST (-0800), gao...@eswincomputing.com wrote:
The stack that save-restore reserves is not well accumulated in stack
allocation and deallocation.
This patch allows less instructions to be used in stack allocation and
deallocation if save-restore enabled,
and also a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107940
--- Comment #4 from laurent.alfonsi at linaro dot org ---
(In reply to Jonathan Wakely from comment #1)
> (In reply to laurent.alfo...@linaro.org from comment #0)
> > This may be linked to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90787.
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100628
--- Comment #3 from Philip Balister ---
I'd also like to note the problem is resolved in the latest release of
gcc-9.5.x Thanks to whoever fixed it!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107940
--- Comment #3 from Jonathan Wakely ---
Thanks, Andrew, I hadn't noticed the See Also links. I agree this looks
related.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107940
--- Comment #2 from Andrew Pinski ---
(In reply to Jonathan Wakely from comment #1)
> (In reply to laurent.alfo...@linaro.org from comment #0)
> > This may be linked to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90787.
> > But, I confirm my
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107940
--- Comment #1 from Jonathan Wakely ---
(In reply to laurent.alfo...@linaro.org from comment #0)
> This may be linked to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90787.
> But, I confirm my toolchain is based on trunk (13.0), and contains
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107929
--- Comment #3 from cqwrteur ---
(In reply to Matthias Kretz (Vir) from comment #2)
> std::experimental::simd has always been implemented with GCC's vector
> extension. Also copy_from and copy_to are implemented with __builtin_memcpy.
The
Hi Gerald,
Excerpts from Gerald Pfeifer's message of November 29, 2022 9:21 pm:
> Hi Iain,
>
> On Tue, 29 Nov 2022, Iain Buclaw via Gcc-patches wrote:
>> This looks obvious, however I don't know how things are generated for
>> the online documentation site in order to say this won't cause any
>>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106581
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107749
--- Comment #3 from CVS Commits ---
The master branch has been updated by Iain Buclaw :
https://gcc.gnu.org/g:d13c359a49291f0a1206adbad4065677010b7e4b
commit r13-4421-gd13c359a49291f0a1206adbad4065677010b7e4b
Author: Iain Buclaw
Date: Mon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107172
H.J. Lu changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
Hi,
This adds an initial body of documentation for the D front-end - other
than the existing documentation for command-line usage/the man page.
Documentation covers code generation choices specific to GNU D - what
attributes are supported, intrinsics, pragmas, predefined versions,
language
Hi,
This patch sorts out the include directories for building the gdc docs -
we don't need to include anything from the toplevel docs directory.
The html output directory has also been renamed from /d/ to /gdc/ to
make it clearer that this is vendor-specific documentation.
Tested by building
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80200
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|WAITING
1 - 100 of 268 matches
Mail list logo
