Host toolchain for building latest gcc release (4.1.1)

gcc-4.1.1. This question expands to all current gcc that will get gcc-4.2 release status in a few months. I would like to thank you in advance Nikolaos Kavvadias -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.

Re: Issue with hard regs

act that i have not included patterns (or code emission routines in "dlx.c") for handling 64-bit moves. Am I missing something else here (not in detail but any coarse grained info)? thanks in advance Nikolaos Kavvadias PS: libgcc2.{c,h} looks OK, both gcc-3.4.1 and current CVS versions (actuall

Some issues regarding a simple RISC backend

s when gcc tries to find a way to properly deal with "muldi3". How can i disable integer long and long long arithmetic for the target? 2) How should I make "gcc" not to expect that the target will deal with floating-point operations? Not even with "SoftFloat" or included

Re: Basic block profiling support in recent GCCs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mike Stump wrote: > On May 16, 2006, at 5:08 AM, Nikolaos Kavvadias wrote: > >> is basic block profiling being dropped out > > > Please use gcov instead. No, gcov isn't going away. > > Thank you Mike and Janis for y

Basic block profiling support in recent GCCs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there is basic block profiling being dropped out from recent GCCs (i mean compiling with "-g -pg -a")? If it is still supported in any of the GCC development branches please let me know. thanks in advance Nikolaos Kavvadias

Re: Optimizations for the MIPS target

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Daney wrote: > Joe Buck wrote: > >> On Thu, May 04, 2006 at 04:31:15PM +0300, Nikolaos Kavvadias >> wrote: >> >>> My question here is: culdn't "-Os" optimization option force >>> .al

Optimizations for the MIPS target

emit the lw,sw instructions for -O3. lb,lbu etc.. are only used by the -Os option. However, i'm not sure that there is a clear code size advantage for using these variants. What I mean is: shouldn't they be used always? thanks in advance Nikolaos Kavvadias -BEGIN PGP SIGNATURE- Versi

Open-source projects supporting GIMPLE

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there are there any open-source projects supporting GIMPLE (e.g. as the input IR for compilation purposes) and specifically focus on: a) tree transformations b) automating the backend development process Thanks in advance Nikolaos Kavvadias

Using only regular register names in emitted assembly

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there how is it possible to emit regular register names (e.g. for the MIPS to use $31 and not $ra) when producing assembly output (with mips-elf-gcc -S)? I want to just use the arithmetic names ($0 to $31). regards Nikolaos Kavvadias -BEGIN

[Fwd: Re: Generating assembly code without macro-instructions]

SIGNATURE- --- Begin Message --- -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > Dave> On 27 February 2006 14:48, Nikolaos Kavvadias wrote: Dave> > Well, yes, it /could/ be done. It would be pretty trivial Dave> > really; you'd just need to go through the insn patterns