On Sun, May 2, 2010 at 11:38 PM, Gerald Pfeifer wrote:
> As http://gcc.gnu.org/ml/gcc-testresults/2010-05/msg00120.html shows,
> *-unknown-freebsd* exhibits tons of failures around LTO.
>
> I dug a bit deeper, and even the most trivial test program
> int main() { }
> fails with
> lto1: internal
Hi all,
I tried to link a pthread application with -static and run into a segfault on
x86, same on powerpc.
I tried gcc 4.4.2 (linux/x86) and 4.0.2 for powerpc-unknown-linux-gnu
For the x86 linux example I got in gdb:
(gdb) bt
#0 0x in ?? ()
#1 0x08094d49 in __cxa_guard_release ()
#
Hi all,
I tried to compile the gcc 4.5.0 version, but got errors with gmp :-(
I did:
k...@mauersegler:~/work/gcc-4.5.0$ cp -pr ../gmp-5.0.1/ ./gmp
k...@mauersegler:~/work/gcc-4.5.0$ cp -pr ../mpfr-2.4.2/ ./mpfr
k...@mauersegler:~/work/gcc-4.5.0$ cp -pr ../mpc-0.8.1/ ./mpc
k...@mauersegler:~/wo
/src/gcc-4.5.0/libgcc/../gcc/config/alpha/vms-gcc_shell_handler.c: In function
'get_dyn_handler_pointer':
/src/gcc-4.5.0/libgcc/../gcc/config/alpha/vms-gcc_shell_handler.c:73:3: error:
'PDSCDEF' undeclared (first use in this function)
/src/gcc-4.5.0/libgcc/../gcc/config/alpha/vms-gcc_shell_handl
Dear all,
I'm working on my a gcc compiler for my own written processor with the help
of SimpleScalar.
I want to remove "srav/slav" (immediate arithmetic shift) from the
instruction set. I explore ss.md file but I didn't see any define_ins for
the mentioned instructions, but they are used in othe
VMS decc$types.h:
typedef unsigned int __size_t;
but with GCC 4.5.0 this preprocesses as:
typedef unsigned int ;
and there are ensuing errors e.g. when compiling gcc/libiberty/regex.c
probably because of:
/usr/local/lib/gcc/alpha-dec-vms/4_5_0/include/stddef.h (it does get includ
On May 3, 2010, at 12:02 PM, Jay K wrote:
>
> /src/gcc-4.5.0/libgcc/../gcc/config/alpha/vms-gcc_shell_handler.c: In
> function 'get_dyn_handler_pointer':
> /src/gcc-4.5.0/libgcc/../gcc/config/alpha/vms-gcc_shell_handler.c:73:3:
> error: 'PDSCDEF' undeclared (first use in this function)
> /src/
On May 3, 2010, at 12:33 PM, Jay K wrote:
>
> VMS decc$types.h:
>
> typedef unsigned int __size_t;
>
> but with GCC 4.5.0 this preprocesses as:
>
> typedef unsigned int ;
>
> and there are ensuing errors e.g. when compiling gcc/libiberty/regex.c
>
> probably because of:
>
> /us
> src/gcc-4.5.0/libiberty/regex.c: In function 'byte_insert_op2':
> /src/gcc-4.5.0/libiberty/regex.c:4279:1: error: unrecognizable insn:
> (insn 62 61 63 5 /src/gcc-4.5.0/libiberty/regex.c:4276 (set (reg:DI 135)
> (plus:SI (subreg/s:SI (reg/v/f:DI 109 [ pfrom ]) 0)
> (const_int
In file included from /src/gcc-4.5.0/libiberty/pex-common.c:23:0:
/src/gcc-4.5.0/libiberty/pex-common.h:73:3: error: expected
specifier-qualifier-list before 'pid_t'
the code:
/* pid_t is may defined by config.h or sys/types.h needs to be
included. */
#if !defined(pid_t) && defined(HAVE_SY
build=i386-darwin
host=alpha-dec-vms
target=alpha-dec-vms
alpha-dec-vms-ar rc ./libiberty.a \
./regex.o ./cplus-dem.o ./cp-demangle.o ./md5.o ./sha1.o ./alloca.o
./argv.o ./choose-temp.o ./concat.o ./cp-demint.o ./crc32.o ./dyn-string.o
./fdmatch.o ./fibheap.o ./filename_cmp.o ./floatfo
I'm guessing that every ".o" in libiberty/Makefile.in should be changed to
$(OBJEXT).
Thanks,
- Jay
> From: jay.kr...@cornell.edu
> To: gcc@gcc.gnu.org
> Subject: gcc 4.5.0 libiberty .o vs. .obj confusion
> Date: Mon, 3 May 2010 11:29:15 +
>
>
> bui
build=i386-darwin
host=alpha-dec-vms
target=alpha-dec-vms
/bin/sh ../libtool --mode=compile alpha-dec-vms-gcc -mbwx -std=gnu99
-DHAVE_CONFIG_H -I. -I/src/gcc-4.5.0/gmp/mpn -I.. -D__GMP_WITHIN_GMP
-I/src/gcc-4.5.0/gmp -DOPERATION_`echo get_d | sed 's/_$//'` -g -O2 -c -o
get_d.lo get_d.c
al
2010/4/27 Diego Novillo :
> On 4/19/10 10:43 , Laurynas Biveinis wrote:
>
>> 1) New API in libiberty for creating of hash tables and splay trees
>> with user-specified callbacks for allocation. Needs libiberty
>> maintainer review.
>> 2) Make gengtype accept variable_size GTY option and output type
On 3 May 2010 10:43, Klaus Rudolph wrote:
> Hi all,
>
> I tried to compile the gcc 4.5.0 version, but got errors with gmp :-(
Hi,
this question is not appropriate on this mailing list, which is for
discussing development of gcc, please take any further questions about
building or using gcc to the
Hi All,
I have tried to write some peephole patterns and I now have some
questions regarding the way it is working.
1. Is that true that if I try to match in the pattern two insns and in
my code between these insns there is another insn which does not have
any dependency connection to the other t
On 3 May 2010 10:37, Klaus Rudolph wrote:
>
> g++ -static -O2 main.cpp /usr/lib/libpthread.a -o linux
You could try -static -pthread instead of specifying the static lib
Please take any follow up questions to the gcc-help list, your
question is not appropriate for this list.
Thanks,
Jonathan
>> Date: Thu, 29 Apr 2010 08:55:56 +0200 (CEST)
>> From: "Jonas Paulsson"
>
>> It feels good to know that the widening mults issue has been
>> resolved
>
> Yes, nice, and as late as last week too, though the patch was
> from February.
>
>> as
>> it was a bit of a disapointment I noted the erratic
I find.
-fms-extentions
On Sun, May 2, 2010 at 22:47, wuyin wrote:
> Please support this grammar.
> http://sourceforge.net/projects/coo/
My advice is to use a language with proper abstraction facilities, like C++.
yazdanbakhsh writes:
> I'm working on my a gcc compiler for my own written processor with the help
> of SimpleScalar.
> I want to remove "srav/slav" (immediate arithmetic shift) from the
> instruction set. I explore ss.md file but I didn't see any define_ins for
> the mentioned instructions, but
Jay K writes:
> proposed/tested fix:
> #ifdef __vms
> #include
> #endif
>
> or similar.
Use #ifdef HAVE_UNISTD_H instead. There are many examples in
libiberty.
Ian
Jay K writes:
> I'm guessing that every ".o" in libiberty/Makefile.in should be changed to
> $(OBJEXT).
Yes.
Ian
roy rosen writes:
> 1. Is that true that if I try to match in the pattern two insns and in
> my code between these insns there is another insn which does not have
> any dependency connection to the other two, Is that true that the
> peephole would not match in this case? (i.e. the insns to match
Hi,
Please assume I'm working with the MIPS. There is a little difference
between the MIPS and what I'm actually working on it. How can I remove
immediate logical shift right/left from the compiler?
I mean If I want the programmer writes an immediate shift, It is compiled to
the two instructions:
yazdanbakhsh writes:
> Please assume I'm working with the MIPS. There is a little difference
> between the MIPS and what I'm actually working on it. How can I remove
> immediate logical shift right/left from the compiler?
> I mean If I want the programmer writes an immediate shift, It is compiled
On 03-05-2010 00:47 wuyin wrote:
struct T{
int n;
};
struct T1{
struct T;
} t;
t.n=1;
Please support this grammar.
I believe it _is_ currently supported with -fms-extensions.
See:
http://gcc.gnu.org/onlinedocs/gcc/Unnamed-Fields.html
Regards,
--
Pedro Pedruzzi
Is it any way that we can chat?
I'm working on my thesis project and a paper. I appreciate it if you would
cooperate in this project.
I have gmail Id "amir.yazdanbakhsh"
and also skype "amir.yazdanbakhsh"
best regards,
yazdanbakhsh wrote:
>
> Hi,
>
> Please assume I'm working with the MIPS. Th
I forget to thank you for your help.
But if I do write your code how compiler knows that it should be put two
instructions instead immediate shift?
I write this piese of code:
###33
(define_insn "lshrsi3"
[(set (match_operand:SI 0 "re
This is the newer version. It works correctly. I just want know is there any
other way.
thanks
***
(define_insn "lshrsi3"
[(set (match_operand:SI 0 "register_operand" "=d")
(lshiftrt:SI (match_operand:SI 1 "register_operand" "d")
yazdanbakhsh writes:
> This is the newer version. It works correctly. I just want know is there any
> other way.
Did you read what I wrote earlier?
http://gcc.gnu.org/ml/gcc/2010-05/msg00048.html
Ian
> It's the encoding of 1.0f (single precision). The point is that we want
> something we can safely compare with 0.0f using floating-point instructions.
> "Safe" means "without generating any kind of exception", so a subnormal
> representation like 0x0001 isn't acceptable. 1.0f seems as good
I recently ended up in a discussion about the -pthread flag at work and
when looking at the documentation I noticed that it is defined onlt for
SPARC and RS/6000/PowerPC.
Additionally -fopenmp and -ftree-parallelize-loops say they are only
supported on targets where -pthread are available.
Now, o
33 matches
Mail list logo
