https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118194
--- Comment #8 from vvinayag at arm dot com ---
(In reply to Sam James from comment #6)
> (In reply to vvinayag from comment #5)
> > (In reply to Sam James from comment #4)
> > > (In reply to Xi Ruoyao from comment #1)
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118194
vvinayag at arm dot com changed:
What|Removed |Added
CC||vvinayag at arm dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99731
vvinayag at arm dot com changed:
What|Removed |Added
CC||vvinayag at arm dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106878
vvinayag at arm dot com changed:
What|Removed |Added
CC||vvinayag at arm dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107620
--- Comment #2 from vvinayag at arm dot com ---
(In reply to Martin Liška from comment #1)
> Confirmed. Btw. what revision do you build and what command do you use?
Could you please clarify what you are referring to, for the revision
Assignee: unassigned at gcc dot gnu.org
Reporter: vvinayag at arm dot com
Target Milestone: ---
I am noticing errors with use of sphinx when building:
Build machine: x86_64-none-linux-gnu
Host: x86_64-none-linux-gnu
Target: aarch64-none-elf or arm-none-eabi
SPHINXBUILD=
make[2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100017
--- Comment #45 from vvinayag at arm dot com ---
(In reply to Jonathan Wakely from comment #44)
> *** Bug 103570 has been marked as a duplicate of this bug. ***
Hi Jonathan,
I see that you plan to fix this soon
(https://gcc.gnu.org/bugzi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100017
vvinayag at arm dot com changed:
What|Removed |Added
CC||vvinayag at arm dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100757
vvinayag at arm dot com changed:
What|Removed |Added
CC||vvinayag at arm dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100379
vvinayag at arm dot com changed:
What|Removed |Added
CC||vvinayag at arm dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96029
vvinayag at arm dot com changed:
What|Removed |Added
CC||vvinayag at arm dot com
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: vvinayag at arm dot com
Target Milestone: ---
The test gcc.dg/atomic/pr65345-4.c causes ICE on arm-none-linux-gnueabihf and
aarch64-none-linux-gnu.
On aarch64-none-linux-gnu:
spawn /obj/gcc/gcc
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: vvinayag at arm dot com
Target Milestone: ---
Internal Compiler Error when compiling glibc/stdio-common/vfprintf-internal.c.
The build configuration is:
BUILD: x86_64/linux
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95700
--- Comment #20 from vvinayag at arm dot com ---
(In reply to vvinayag from comment #18)
> (In reply to Ilya Leoshkevich from comment #17)
> > Created attachment 48917 [details]
> > aarch64 native build fix
> >
> &g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95700
--- Comment #19 from vvinayag at arm dot com ---
Created attachment 48921
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48921&action=edit
Add -std=c++11 to the aarch64 native build fix
This patch adds CXX="$CXX -std=c++11&q
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95700
--- Comment #18 from vvinayag at arm dot com ---
(In reply to Ilya Leoshkevich from comment #17)
> Created attachment 48917 [details]
> aarch64 native build fix
>
> Could you please try the attached patch? It fixed the issue
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95700
--- Comment #15 from vvinayag at arm dot com ---
(In reply to Ilya Leoshkevich from comment #14)
> gcc113 has 4.8.4, which is a bit newer. But in any case, according to
> https://gcc.gnu.org/projects/cxx-status.html, gcc should support n
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95700
--- Comment #13 from vvinayag at arm dot com ---
(In reply to Ilya Leoshkevich from comment #12)
> I managed to bootstrap and regtest upstream commit 6e41c27bf549 on gcc113
> farm machine.
>
> Two questions:
>
> - What is yo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95700
vvinayag at arm dot com changed:
What|Removed |Added
CC||vvinayag at arm dot com
ty: normal
Priority: P3
Component: libfortran
Assignee: unassigned at gcc dot gnu.org
Reporter: vvinayag at arm dot com
Target Milestone: ---
I am seeing these implicit declaration errors when building gcc for
arm-none-eabi targets.
In file src/gcc/libgfortr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94763
vvinayag at arm dot com changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94763
--- Comment #2 from vvinayag at arm dot com ---
(In reply to Christophe Lyon from comment #1)
> How do you configure GCC, and what flags to you use to run the tests?
> They work for me, on several configuration of arm-non-eabi-gcc as
&
: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: vvinayag at arm dot com
Target Milestone: ---
Many tests are UNRESOLVED on arm-none-eabi.
UNRESOLVED: g++.dg/abi/abi-tag1.C -std=gnu++14 scan-assembler _Z1fB3barB3fooi
UNRESOLVED: g++.dg/abi/abi-tag1.C -std=gnu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92643
vvinayag at arm dot com changed:
What|Removed |Added
CC||vvinayag at arm dot com
24 matches
Mail list logo