https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68491
--- Comment #10 from Christos Zoulas ---
On Jun 27, 4:26pm, gcc-bugzi...@gcc.gnu.org ("luto at kernel dot org") wrote:
-- Subject: [Bug target/68491] libgcc calls __get_cpuid with 0 level breaks o
| I'm a bit late to the party, but this patch s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68491
--- Comment #2 from Christos Zoulas ---
Created attachment 41284
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41284&action=edit
Amended cpuid patch.
Here's an amended patch against the trunk. Also sent mail to gcc-patches@
Priority: P3
Component: libgcc
Assignee: unassigned at gcc dot gnu.org
Reporter: christos at zoulas dot com
Target Milestone: ---
http://nxr.netbsd.org/xref/src/external/gpl3/gcc/dist/libgcc/config/i386/cpuinfo.c#284
calls __get_cpuid with 0 level, then we end up in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67956
--- Comment #6 from Christos Zoulas ---
great, thank you. since this is tracked already you can close it if you want.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67956
--- Comment #4 from Christos Zoulas ---
I believe that -pedantic enables other "pedantic" warnings which I don't belive
I want. I can add a specific printf format that does not accept %m, but I would
still need to add a syslog format that does (a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67956
--- Comment #2 from Christos Zoulas ---
something is wrong with the bug tracking system, when posting a bug with an
attachment as the first post; this is how the dup got created.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67957
--- Comment #1 from Christos Zoulas ---
Created attachment 36504
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36504&action=edit
patch
ormal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: christos at zoulas dot com
Target Milestone: ---
According to TOG
(http://pubs.opengroup.org/onlinepubs/009695399/functions/fprintf.html), %m is
not a legal formatting character for pri
ormal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: christos at zoulas dot com
Target Milestone: ---
Created attachment 36503
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36503&action=edit
patch
According to TOG
(http://pubs.o
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59674
--- Comment #6 from Christos Zoulas ---
On Jan 4, 8:42pm, gcc-bugzi...@gcc.gnu.org ("mikpelinux at gmail dot com")
wrote:
-- Subject: [Bug c/59674] On m68k and vax variables stack variables with > MA
| That is correct, m68k-linux has looser alig
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59674
--- Comment #4 from Christos Zoulas ---
On Jan 4, 5:22pm, gcc-bugzi...@gcc.gnu.org ("mikpelinux at gmail dot com")
wrote:
-- Subject: [Bug c/59674] On m68k and vax variables stack variables with > MA
| http://gcc.gnu.org/bugzilla/show_bug.cgi?id
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59674
--- Comment #2 from Christos Zoulas ---
On Jan 4, 11:20am, gcc-bugzi...@gcc.gnu.org ("mikpelinux at gmail dot com")
wrote:
-- Subject: [Bug c/59674] On m68k and vax variables stack variables with > MA
| http://gcc.gnu.org/bugzilla/show_bug.cgi?id
MED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: christos at zoulas dot com
Thie simple example:
struct foo {
const char *place;
long long time;
};
extern int goo(struct foo *);
int foo(void);
int
13 matches
Mail list logo
