https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69381
--- Comment #3 from Claudiu Zissulescu ---
This is a very old issue. I see no problem with the latest gcc14.x.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113954
--- Comment #5 from Claudiu Zissulescu ---
Hi guys,
I am working on a patch which removes mlra option, making the LRA default. I'll
try to push it somewhere next week.
Cheers,
Claudiu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104154
Claudiu Zissulescu changed:
What|Removed |Added
CC||claziss at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40883
Bug 40883 depends on bug 90120, which changed state.
Bug 90120 Summary: inconsistent punctuation in translation messages
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90120
What|Removed |Added
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90120
Claudiu Zissulescu changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92845
--- Comment #1 from Claudiu Zissulescu ---
Although the FDCMP (the double precision floating point compare instruction) is
added to the compiler, it is not properly used via cstoredi pattern.
A patch can be this one:
index b592f25afce..bd44030b4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78804
--- Comment #17 from Claudiu Zissulescu ---
Removing FLOAT_BIT_ORDER_MISMATCH seems it doesn't affect ARC backend as well.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89838
--- Comment #2 from Claudiu Zissulescu ---
Patch pushed to mainline r272643.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79869
--- Comment #3 from Claudiu Zissulescu ---
DOC is string that shortly describes an machine dependent option. This string
is used to throw an warning/error when the underling option is not available
for a specific architecture, which can be arcem,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90120
--- Comment #3 from Claudiu Zissulescu ---
Added a patch to solve upper/lower issue:
https://gcc.gnu.org/ml/gcc-patches/2019-04/msg00696.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90120
Claudiu Zissulescu changed:
What|Removed |Added
CC||claziss at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90103
--- Comment #1 from Claudiu Zissulescu ---
Probably,this patch needs to be backported:
[ARC] Update fma expansions.
Accept at most a single constant for fma patterns.
gcc/
2018-03-21 Claudiu Zissulescu
* config/
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89877
--- Comment #4 from Claudiu Zissulescu ---
Backported to gcc 8 branch revision 270200.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89838
--- Comment #1 from Claudiu Zissulescu ---
It is confirmed also in gcc mainline branch:
tst-tls1.c: In function ‘check_s’:
tst-tls1.c:65:1: error: unrecognizable insn:
(insn 36 35 37 6 (set (reg/f:SI 163)
(plus:SI (plus:SI (reg:SI 25 r25
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85968
--- Comment #4 from Claudiu Zissulescu ---
Yes we can close it, no need for backporting.
//Claudiu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88001
--- Comment #6 from Claudiu Zissulescu ---
The dejagnu tests for ARC look alright. No extra failures.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85968
Claudiu Zissulescu changed:
What|Removed |Added
CC||claziss at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88001
Claudiu Zissulescu changed:
What|Removed |Added
CC||claziss at gmail dot com
-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: claziss at gmail dot com
Target Milestone: ---
ASMCONS cannot handle CONST (UNSPEC) properly, leading to a wrong
output.
I have the following rtl before asmcons pass:
(insn 8 13 9 2 (set (reg:SI 157 [ list
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78804
--- Comment #12 from Claudiu Zissulescu ---
(In reply to Oleg Endo from comment #11)
> I'm confused. Who is actually the effective maintainer of ARC? All the
> patches on gcc-patches seem to go like
Hi,
I am the effective ARC maintainer, jus
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71749
--- Comment #4 from Claudiu Zissulescu ---
If it is ok with you, I will do it in ur name as well. But first, let me see
how the nightly goes.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71749
--- Comment #2 from Claudiu Zissulescu ---
Proposed patch for mainline:
diff --git a/gcc/config/arc/arc.h b/gcc/config/arc/arc.h
index 5cc9dc1..d270390 100644
--- a/gcc/config/arc/arc.h
+++ b/gcc/config/arc/arc.h
@@ -62,7 +62,8 @@ along with GCC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71749
Claudiu Zissulescu changed:
What|Removed |Added
CC||claziss at gmail dot com
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: claziss at gmail dot com
Target Milestone: ---
I've been trying the following simple test case on latest gcc, and it seems to
produce unwanted unaligned accesses for bit-fields.
Test cases:
struct lock_chain {
uns
24 matches
Mail list logo
