Hi,
thanks for your hints!
Sorry for being unclear in my first mail. You were right, it
was the C library that was missing. As i've provided newlib
now, i now got a working compiler for C, C++ and Java.
Best regards,
Torsten.
Sebastian Pop <[EMAIL PROTECTED]> writes:
> I'd like to ask GCC users in general: how many are using these params?
We use them at my current employer, mainly to remove limits which were
imposed to keep compile time under control. We have code which needs
to run as fast as possible, for which com
Kai Henningsen wrote:
The point is that there are two different kinds of value range
calculations. You have value range information from program flow, and you
have value range information from types.
You want 'Valid optimization to ignore range information from types,
because that's what
On Sun, 2005-08-14 at 01:12 +0200, Sebastian Pop wrote:
> Joe Buck wrote:
> > The problem with using time as a cutoff is that you then get results that
> > can't be reproduced reliably. Better to count something that is a feature
> > of the algorithm, e.g. number of executions of some inner loop,
I'm porting the GCC 4.0.2 (2005-08-11 snapshot) to a new VLIW architecture.
I figured out the `free_bb_for_insn()' is called before the reorg pass,
and I would like to use the CFG in the reorg pass for a reason.
The reason is:
I would like to change flag_schedule_insns_after_reload to 0 by th
Torsten Mohr wrote:
configure: WARNING: No native atomic operations are provided for this \
platform.
configure: WARNING: They cannot be faked when thread support is disabled.
configure: WARNING: Thread-safety of certain classes is not guaranteed.
These are just warnings, and won't stop the bui
Ling-hua Tseng wrote:
> Are there any ways to tell GCC that don't group an jump_insn with
> other insns when structural hazard occured?
Probably multiple ways, depending on what exactly the problem is.
I'd suggest using -da -fsched-verbose=2 and looking at the scheduling
info printed in the sched
Kevin McBride wrote:
I have been having comparison errors while building a native 4.0.1
compiler for my Fedora Core 4 system.
Running
cmp c-pragma.o stage2/c-pragma.o
on your provided files says that they identical. If you are getting
comparison failures on these files, then perhaps your "c
/home/gj/Projects/gcc/build/gcc/xgcc -B/home/gj/Projects/gcc/build/gcc/
-B/usr/local/gcc4.0/i686-pc-linux-gnu/bin/
-B/usr/local/gcc4.0/i686-pc-linux-gnu/lib/
-isystem /usr/local/gcc4.0/i686-pc-linux-gnu/include
-isystem /usr/local/gcc4.0/i686-pc-linux-gnu/sys-include -O2 -DIN_GCC-W
-Wall -
Joe Buck wrote:
> The problem with using time as a cutoff is that you then get results that
> can't be reproduced reliably. Better to count something that is a feature
> of the algorithm, e.g. number of executions of some inner loop, number of
> nodes visited, or the like,
On the other hand, it
"Balaji V. Iyer" <[EMAIL PROTECTED]> writes:
>I am adding a DFA scheduler for OpenRISC Processor in GCC. (I have not
> changed anything else). I don't see a difference in assembly at all. I
> would like to know how to make it recognize that there is a DFA
> scheduler.
Which sources are you wo
Hi Everyone,
I am adding a DFA scheduler for OpenRISC Processor in GCC. (I have not
changed anything else). I don't see a difference in assembly at all. I
would like to know how to make it recognize that there is a DFA
scheduler. I have already did the following line
(include "OpenRISC_DFA")
I
Christian Joensson wrote:
configure: loading cache ./config.cache
configure: error: `LDFLAGS' was not set in the previous run
configure: error: changes in the environment can compromise the build
configure: error: run `make distclean' and/or `rm ./config.cache' and start over
This happens somet
Paul Brook wrote:
We already have TYPE_STRING_FLAG used on array types. Maybe it would it make
sense to use that?
That sounds like an excellent choice. dbxout.c and dwarf2out.c already
check TYPE_STRING_FLAG to distinguish strings from arrays.
--
Jim Wilson, GNU Tools Support, http://www.spe
Snapshot gcc-4.1-20050813 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.1-20050813/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.1 CVS branch
with the following options: -D2005-08-13 17:43 UTC
You'll
On Sat, Aug 13, 2005 at 09:40:11AM -0400, Daniel Berlin wrote:
>
> >
> > Should I open a PR?
> Yes
OK, this is now bug #23378. Please let me know if you need
more information.
Cheers,
Martin
Hello,
> > The other thing we could try to do is put virtual variables in loop-closed-
> > form, at least just before the vectorizer, and at least just for some
> > loops. Does this sound reasonabale? (By the way, why don't we keep virtual
> > variables in loop-closed-form?)
>
> We used to, nobod
> A possible way to solve this problem is to add a single-bit flag to
> INTEGER_TYPE nodes that indicates whether this is actually a character
> type. Then dwarf2out.c could just check the flag to determine what
> debug info to emit. It looks like we have a number of flag bits that
> aren't being
I have been having comparison errors while building a native 4.0.1
compiler for my Fedora Core 4 system. I checked the flags for a file I
randomly chose, c-pragma.c, and the flags don't differ from initial
build of xgcc to stage2. I have included a tarball of the object files
for c-pragma.c and a
>
> Should I open a PR?
Yes
>
> Cheers,
> Martin
Mike Stump wrote:
On Aug 12, 2005, at 3:45 PM, Laurent GUERBY wrote:
Isn't it possible to attach some information on a comparison
statement that tells code generation never to never
optimize away this particular comparison even if it
seems to be able to prove it is always true or false?
Coug
Hi,
a few days ago I noticed that the current mainline produces much worse
code for one of my time-critical codes than it did a few weeks ago.
After some testing I found out that the regression was introduced
into CVS between the timestamps "-D 20050729 22:00:00 UT" and
"-D 20050729 23:00:00 UT",
Hi,
i try to set up an extended tool chain for --target=v850-unknown-elf.
I configured and installed binutils-2.16, that went fine.
Configuring and building gcc-3.4.4, gcc-4.0.1 all fail at libstdc++-v3.
It seems that there is no "atomic operation provided for this system":
configure: WARNING:
23 matches
Mail list logo
