Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: teo.samarzija at gmail dot com
Target Milestone: ---
Hey, guys!
So, I think I've found a bug in GCC 8.3.1 that occurs on Linux. Here is a
simple test case:
int printf(const char*,...);
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95652
--- Comment #1 from Teo Samarzija ---
Possibly related, "as --version" prints:
GNU assembler (GNU Binutils) 2.33.1
Copyright (C) 2019 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GN
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95652
--- Comment #3 from Teo Samarzija ---
(In reply to Andrew Pinski from comment #2)
> This looks closer to a dup of bug 87986.
>
> Basically -masm=intel is not always working.
When does it occur? Maybe we can determine when it can occur and warn
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95652
--- Comment #5 from Teo Samarzija ---
(In reply to Uroš Bizjak from comment #4)
> (In reply to Teo Samarzija from comment #3)
> > Besides, how does CLANG compile that same code fine, also under Linux and
> > with "-masm=intel"? Maybe you can copy
nt: c
Assignee: unassigned at gcc dot gnu.org
Reporter: teo.samarzija at gmail dot com
Target Milestone: ---
So, the C library I am using to cross-compile programs from Linux to DOS
apparently doesn't support the "log2" function, and I tried to polyfill it:
#i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95800
--- Comment #2 from Teo Samarzija ---
(In reply to Jakub Jelinek from comment #1)
> Perhaps log2 is in DJGPP a macro (which the C standard allows)?
> In that case, you either need to #undef that macro, or
> use double (log2)(double x) { ... }
I
