Hi -
I am trying to build GCC 4.9.4, with originally only GCC 4.4.7, on
a Linux RHEL6 (i686) lxc container under x86_64 Centos-7 -
so I cloned and built:
https://github.com/gcc-mirror/gcc/tree/releases/gcc-4.9
with configure flags:
Target: i686-redhat-linux
Configured with: ../configu
This problem turned out to be because the objects in
libasan.a of gcc-6-branch are built with -fPIC / -DPIC :
if 'PIC' is defined, the code in asan_linux.c is
assuming it has been dynamically loaded , and so
does not allow libasan.so NOT to be the first
required dynamic library. But adding '-lasa
To me it looks like the definition of 'real_sigaction'
in 'asan_interceptors.cc' is actually going to
recursively call itself - so I tried patching
libsanitizer:
{BEGIN PATCH:
Index: asan/asan_interceptors.cc
===
--- asan/asan_interc
Good day -
Attempts to build latest GCC gcc-6-branch version from SVN ( Revision
260441 ), with the GCC 6.4.1 from the last time I built it ( git
commit starting '4f2cbe2' ), now fail in 'make check' , on a Linux
x86_64 host (RHEL 7.5, glibc 2.17) :
When 'pr59063-2.c' is built with the '-static-
I really do not think a '-Wpedantic -Wconversion' warning should
be generated for the following code, but it is
(with GCC 6.4.1 and 7.3.1 on RHEL-7.5 Linux) :
$ echo '
typedef unsigned short U16_t;
static void f(void)
{ U16_t a = 1;
a-=1;
}' > t.C;
$ g++ -std=c++14 -Wall -Wextra -pedant
On 01/04/2018, Max Filippov wrote:
> On Sun, Apr 1, 2018 at 4:34 AM, Jason Vas Dias
> wrote:
>> In C++ however, it does not compile :
>>
>> $ g++ -g -std=gnu++11 -x c++ -c t.c
>> t.c:5:8: error: 'void bar()' aliased to undefined symbol 'foo'
&g
Good day -
I'm trying to understand why this code compiles fine
in 'gcc -std=gnu11' mode, but not in
'g++ -std=g++11' mode
(so far tried with gcc/g++ 5.4.0 , 7.3.1 on x86_64 linux) :
'
static inline __attribute__((always_inline))
void foo(void){}
static inline __attribute
On Mon, Mar 11, 2013 at 10:07 PM, David Edelsohn wrote:
> On Mon, Mar 11, 2013 at 3:46 PM, Jason Vas Dias
> wrote:
>> Hi - I wonder if anyone could please tell me if gcc's thread local
>> storage support is meant to be enabled on AIX or not -
>> I've built gcc
lation
documentation (it does not appear to be) ? Any plans to enable it in
near future ?
Thanks in advance for any replies,
Jason Vas Dias
#include
#include
struct state
{
unsigned char
bit1:1 , bit2:1 , bit3:1 , bit4:1
, bit5:1 , bit6:1
