https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98743
--- Comment #3 from Kito Cheng ---
Seems like g:3e60ddeb8220ed388819bb3f14e8caa9309fd3c2 is the real root cause
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98786
Richard Biener changed:
What|Removed |Added
Last reconfirmed||2021-01-22
Status|UNCONFIRM
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98784
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |8.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98519
Alan Modra changed:
What|Removed |Added
CC||amodra at gmail dot com
--- Comment #18 fro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98348
--- Comment #18 from Hongtao.liu ---
Fix on trunk sofar, as jakub suggests, not back port to gcc10.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98348
--- Comment #17 from CVS Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:ee78c20e74d30284fee36e22a64e86e45e676029
commit r11-6849-gee78c20e74d30284fee36e22a64e86e45e676029
Author: liuhongt
Date: Fri Dec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96891
--- Comment #2 from CVS Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:ee78c20e74d30284fee36e22a64e86e45e676029
commit r11-6849-gee78c20e74d30284fee36e22a64e86e45e676029
Author: liuhongt
Date: Fri Dec 1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98786
Bug ID: 98786
Summary: ICE: SSA corruption (Unable to coalesce ssa_names 2
and 10 which are marked as MUST COALESCE.)
Product: gcc
Version: 11.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95095
--- Comment #5 from Fangrui Song ---
Linux kernel
include/asm-generic/vmlinux.lds.h currently has
#define TEXT_TEXT \
ALIGN_FUNCTION(); \
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98697
--- Comment #4 from Hongtao.liu ---
(In reply to Hongtao.liu from comment #3)
> (In reply to Christophe Lyon from comment #2)
> > Why would this be different from right shift, where we don't miss the
> > optimization?
>
> It's supposed to be han
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98785
Bug ID: 98785
Summary: _Unwind_ForcedUnwind going through a non-empty
exception specification
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98697
--- Comment #3 from Hongtao.liu ---
(In reply to Christophe Lyon from comment #2)
> Why would this be different from right shift, where we don't miss the
> optimization?
It's supposed to be handled in vect_recog_over_widening_pattern, but failed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97966
Marek Polacek changed:
What|Removed |Added
Summary|[10/11 Regression] |[10 Regression]
|maybe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97966
--- Comment #4 from CVS Commits ---
The master branch has been updated by Marek Polacek :
https://gcc.gnu.org/g:bca467e56fe111fa6d876656c60d5704065e83fe
commit r11-6848-gbca467e56fe111fa6d876656c60d5704065e83fe
Author: Marek Polacek
Date: Tu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95095
--- Comment #4 from Segher Boessenkool ---
On Sat, Jan 16, 2021 at 09:00:56PM +, i at maskray dot me wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95095
>
> --- Comment #3 from Fangrui Song ---
> (In reply to Segher Boessenkool from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91707
Martin Sebor changed:
What|Removed |Added
Last reconfirmed|2019-09-09 00:00:00 |2021-1-21
Known to fail|10.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98771
Martin Sebor changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98659
--- Comment #5 from Marek Polacek ---
(In reply to Matthias Klose from comment #4)
> I got reports for this issue for the gcc-10 branch as well. Please could you
> consider a backport?
That must be a different problem, perhaps 98333.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96963
Martin Sebor changed:
What|Removed |Added
Last reconfirmed|2020-09-07 00:00:00 |2021-1-21
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98659
Matthias Klose changed:
What|Removed |Added
CC||doko at debian dot org
--- Comment #4 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94655
Martin Sebor changed:
What|Removed |Added
Keywords||patch
--- Comment #15 from Martin Sebor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98784
--- Comment #3 from Eric Botcazou ---
> So -fPIE is not used here but there is a side effect when the patch is
> applied.
You need to look at the output of 'gcc -v' to be sure of that.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98784
--- Comment #2 from Romain Naour ---
Hello,
The kernel and userland are built with the same toolchain, but this is the
userpace program (such busybox) that crash.
Busybox is built with the following flags:
Toolchain wrapper executing:
'qem
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97969
--- Comment #22 from Vladimir Makarov ---
(In reply to Vladimir Makarov from comment #21)
> Additional fix for PR98722 is necessary for this PR.
>
> 4334b524274203125193a08a8485250c41c2daa9
Sorry, one more fix for PR98777 is necessary for the P
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98777
--- Comment #2 from CVS Commits ---
The master branch has been updated by Vladimir Makarov :
https://gcc.gnu.org/g:68ba1039c7daf0485b167fe199ed7e8031158091
commit r11-6844-g68ba1039c7daf0485b167fe199ed7e8031158091
Author: Vladimir N. Makarov
D
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98784
Eric Botcazou changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88443
Bug 88443 depends on bug 95353, which changed state.
Bug 95353 Summary: [10 Regression] spurious -Wstringop-overflow writing to a
trailing array plus offset
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95353
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95353
Martin Sebor changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96725
Martin Sebor changed:
What|Removed |Added
Blocks|88443 |97048
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94335
Martin Sebor changed:
What|Removed |Added
Last reconfirmed|2020-03-26 00:00:00 |2021-1-21
--- Comment #10 from Martin Seb
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94655
Martin Sebor changed:
What|Removed |Added
Status|NEW |ASSIGNED
See Also|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98784
Bug ID: 98784
Summary: [gcc 8.4/9.3/10] sparcv8 regression
Product: gcc
Version: 10.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96188
Martin Sebor changed:
What|Removed |Added
Last reconfirmed|2020-07-13 00:00:00 |2021-1-21
Known to fail|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98129
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Attachment #49687|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98463
Marek Polacek changed:
What|Removed |Added
CC||gcc-bugs at marehr dot
dialup.fu-b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96863
Marek Polacek changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96963
Martin Sebor changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98777
--- Comment #1 from Vladimir Makarov ---
Thank you for reporting this. I've reproduced the bug on riscv64 and started to
work on fixing it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96623
--- Comment #4 from Marek Polacek ---
And an extended test to check that various variables are in scope:
constexpr int x = 0;
struct A {
int a1;
void foo (int p) {
int foovar;
struct B {
int b1;
void bar1 () noexcept(x);
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71879
Patrick Palka changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71879
--- Comment #3 from CVS Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:f645da0e4ab9438dfd0c047c710c7ec6a7d6d8f3
commit r11-6842-gf645da0e4ab9438dfd0c047c710c7ec6a7d6d8f3
Author: Patrick Palka
Date: Th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98783
Martin Liška changed:
What|Removed |Added
Ever confirmed|0 |1
Assignee|unassigned at gcc do
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98573
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90248
--- Comment #15 from Jakub Jelinek ---
Created attachment 50024
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50024&action=edit
gcc11-pr90248.patch
So, I think at minimum we want this, i.e. turn the bogus simplifications into
simplificati
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63426
Bug 63426 depends on bug 98624, which changed state.
Bug 98624 Summary: UBSAN: gcc/cp/module.cc:5895:29: runtime error: member call
on null pointer of type 'struct module_state'
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98624
What
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98624
Nathan Sidwell changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98624
--- Comment #4 from CVS Commits ---
The master branch has been updated by Nathan Sidwell :
https://gcc.gnu.org/g:7944753fad501194eb8a828d6b74270e79d14a4d
commit r11-6841-g7944753fad501194eb8a828d6b74270e79d14a4d
Author: Nathan Sidwell
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98573
Paul Thomas changed:
What|Removed |Added
CC||pault at gcc dot gnu.org
Assigne
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97742
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98618
Wilco changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98618
--- Comment #7 from CVS Commits ---
The releases/gcc-8 branch has been updated by Wilco Dijkstra
:
https://gcc.gnu.org/g:c9569046bd8ba2671833d600b3bdbdb7de593873
commit r8-10736-gc9569046bd8ba2671833d600b3bdbdb7de593873
Author: Wilco Dijkstra
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98730
--- Comment #4 from rsandifo at gcc dot gnu.org
---
Hmm, yeah, looks like it might be a cost issue then.
arm_rtx_costs_internal seems to give CONST_VECTOR
a cost of 1 or 4 instructions, whereas a zero CONST_VECTOR
is free in this context.
Altho
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97597
Jason Merrill changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98531
--- Comment #5 from Nathan Sidwell ---
Created attachment 50022
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50022&action=edit
reduced testcase, this is not solaris-specific, but solaris happened to tickle
it uniquely
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97981
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98672
--- Comment #3 from Jakub Jelinek ---
Fixed on the trunk. I think we need to backport this at least to 10.3
eventually.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98672
--- Comment #2 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:0fb7aa205afebe178c06683037ccd4c41104337a
commit r11-6840-g0fb7aa205afebe178c06683037ccd4c41104337a
Author: Jakub Jelinek
Date: Th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92095
--- Comment #10 from Eric Botcazou ---
> This patch produce a regression on sparcv8 SS10 platform.
>
> In Buildroot we have a defconfig qemu_sparc_ss10_defconfig that was working
> (booting) with gcc 7.4, 8.3 and 9.2. But it doesn't boot anymore
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98255
--- Comment #13 from Jakub Jelinek ---
Created attachment 50021
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50021&action=edit
gcc11-pr98255.patch
The full patch would be I think this. Am going to bootstrap/regtest it just to
see what i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98730
--- Comment #3 from Christophe Lyon ---
At expand time, we have:
(insn 13 12 14 2 (set (reg:V2SI 121 [ _11 ])
(neg:V2SI (eq:V2SI (subreg:V2SI (reg:DI 116 [ _6 ]) 0)
(subreg:V2SI (reg:DI 118 [ _8 ]) 0 "arm_neon.h":2404:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98772
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2021-01-21
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98689
John David Anglin changed:
What|Removed |Added
Summary|FAIL: |[11 Regression] FAIL:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93385
--- Comment #39 from Jakub Jelinek ---
What happened to that patch series? Has it been committed without showing it
up in the PR, something else?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98730
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
CC||rsandifo at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98325
seurer at gcc dot gnu.org changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLV
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98783
Bug ID: 98783
Summary: Wrong ouput of "-O3 -Q --help=optimizers" on gcc
built with --enable-frame-pointer
Product: gcc
Version: 10.2.0
Status: UNCONFIRMED
Seve
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98255
Jakub Jelinek changed:
What|Removed |Added
CC||ebotcazou at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98697
--- Comment #2 from Christophe Lyon ---
Why would this be different from right shift, where we don't miss the
optimization?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98782
James Greenhalgh changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98782
Bug ID: 98782
Summary: IRA artificially creating spills due to BB frequencies
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Keywords: ra
Severity: normal
Prior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98255
--- Comment #11 from Richard Biener ---
(In reply to Richard Biener from comment #9)
> (In reply to Jakub Jelinek from comment #8)
> > 503 poly_offset_int woffset
> > 504 = wi::sext (wi::to_poly_offset (index)
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98255
--- Comment #10 from Martin Jambor ---
OK, adding an additional check whether tree_could_trap_p is of course easy.
I'll wait a little while if the discussion about get_ref_base_and_extent
perhaps leads to a different solution but if not, I will
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98255
--- Comment #9 from Richard Biener ---
(In reply to Jakub Jelinek from comment #8)
> 503 poly_offset_int woffset
> 504 = wi::sext (wi::to_poly_offset (index)
> 505 - wi::to_pol
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98255
--- Comment #8 from Jakub Jelinek ---
503 poly_offset_int woffset
504 = wi::sext (wi::to_poly_offset (index)
505 - wi::to_poly_offset (low_bound),
506
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98255
--- Comment #7 from Martin Jambor ---
Even our constant folding thinks the unsigned expression wraps around. If I
tell SRA to fold the expression if the base is a string_cst, the invalid
dereference is avoided. My experiment was (I am not propo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98255
--- Comment #6 from Jakub Jelinek ---
get_ref_base_and_extent is not the right API to check for the UBs caused by out
of bounds accesses, tree_could_trap_p is.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95693
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98255
--- Comment #5 from Martin Jambor ---
Right, the issue is that SRA depends on get_ref_base_and_extent to figure out
what is being accessed (and so whether it is safe) and that function believes
the load is safely from within the array.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98773
Rainer Orth changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98348
--- Comment #16 from Hongtao.liu ---
(In reply to Jakub Jelinek from comment #15)
> I haven't seen the patch posted to gcc-patches, have I missed it?
> Patch review should happen there.
https://gcc.gnu.org/pipermail/gcc-patches/2021-January/5629
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96372
--- Comment #3 from CVS Commits ---
The master branch has been updated by Andrea Corallo :
https://gcc.gnu.org/g:0568f801effcea6f4e066c40bc346513d6b946c5
commit r11-6836-g0568f801effcea6f4e066c40bc346513d6b946c5
Author: Andrea Corallo
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98772
--- Comment #3 from Richard Biener ---
But the issue seems to be
t.c:3:22: note: ==> examining statement: _34 = *pix1_19;
t.c:3:22: missed: permutation requires at least three vectors _34 = *pix1_19;
t.c:3:22: missed: unsupported load perm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98738
--- Comment #10 from Jakub Jelinek ---
I've been wondering whether it wouldn't be best to pass through
omp_eventhandle_t the pointer to the gomp_task rather than some particular
semaphore and in omp_fulfill_event then decide based on that task,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63426
Bug 63426 depends on bug 98624, which changed state.
Bug 98624 Summary: UBSAN: gcc/cp/module.cc:5895:29: runtime error: member call
on null pointer of type 'struct module_state'
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98624
What
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98624
Nathan Sidwell changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98738
--- Comment #9 from Kwok Yeung ---
I have a patch for this now. In addition to posting other semaphores in
omp_fulfill_event, GOMP_taskwait also needs to be made aware of detached tasks.
Also, task_running_count should not include completed tasks
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98530
Nathan Sidwell changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98530
--- Comment #4 from CVS Commits ---
The master branch has been updated by Nathan Sidwell :
https://gcc.gnu.org/g:3c1cf7350bff6ba03faaa61b44d74bf8a06c6543
commit r11-6834-g3c1cf7350bff6ba03faaa61b44d74bf8a06c6543
Author: Nathan Sidwell
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98255
--- Comment #4 from Jakub Jelinek ---
The return n[0][3][-2U]; access is UB in the program, so if it would be
reached, it can do anything, but the important thing is that it is guarded with
while (g)
where g is always 0 during the exection of the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98618
--- Comment #6 from CVS Commits ---
The releases/gcc-9 branch has been updated by Wilco Dijkstra
:
https://gcc.gnu.org/g:1e18f4bbd8318db1e606f7092a224e4bb21a8a26
commit r9-9193-g1e18f4bbd8318db1e606f7092a224e4bb21a8a26
Author: Wilco Dijkstra
D
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98255
--- Comment #3 from Martin Jambor ---
So SRA sees statements:
n[0][2] = "\t\x02\b";
and later
_11 = n[0][3][4294967294];
The latter loads a scalar sitting inside what the store above
initialized (according to get_ref_base_and_extent) and so
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98778
--- Comment #3 from jbeulich at suse dot com ---
(In reply to Jakub Jelinek from comment #2)
> In particular it is up to the inline asm writer to ensure that the result is
> PIC compatible through a wise choice of constraints etc.
Perhaps the des
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97627
--- Comment #9 from bin cheng ---
(In reply to Jakub Jelinek from comment #8)
> Still broken on current 10 branch, as written works fine on the trunk due to
> the C++ FE loop changes.
> Bin, did you have time to look into this yet?
I am very sor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97627
--- Comment #8 from Jakub Jelinek ---
Still broken on current 10 branch, as written works fine on the trunk due to
the C++ FE loop changes.
Bin, did you have time to look into this yet?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97960
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98690
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
Sta
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98255
--- Comment #2 from Jakub Jelinek ---
Martin, can you please have a look? Thanks.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98295
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98348
--- Comment #15 from Jakub Jelinek ---
I haven't seen the patch posted to gcc-patches, have I missed it?
Patch review should happen there.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98778
--- Comment #2 from Jakub Jelinek ---
In particular it is up to the inline asm writer to ensure that the result is
PIC compatible through a wise choice of constraints etc.
1 - 100 of 135 matches
Mail list logo