Paolo Bonzini wrote:
Compared to the slow idivl, abs could be negligible, right. However, abs
does introduce new data dependence which might add a noticeable cost.
Is there an abs instruction in the i386 instruction set?
No, the closest thing (input in eax, output in edx) is
cltq
You're right, this isn't the correct list for this question, try posting
it to gcc-help
Francesco Montorsi wrote:
Maybe this is not the right list for such question?
Should I directly use gcc bugzilla?
Thanks,
Francesco
Francesco Montorsi ha scritto:
Hi all,
I'm getting a lot of
It would take a massive target-specific backend hack to make that
happen, as GCC currently only supports flat address spaces. ;-)
Rémy Saissy wrote:
Hi everybody,
I'm looking for gcc support of x86-32 segment registers but the only information
I've found about it is in this old thread:
The gen* family of executables is used during the build process to make
various .h files from the .md files for the chosen target (and nowhere
else AFAIK)
sean yang wrote:
If we do a search of main function in gcc4..0.2/gcc directory, we can
find several.
I understand collect2.c--collect2,
Most existing GCC ports for microcontrollers rely on a matching Binutils
port in order to provide an assembler (GAS) and linker (GNU ld). GCC
itself always produces assembler output (which may or may not be saved
to a file).
Colm O' Flaherty wrote:
All,
I've been thinking a bit more about
I'll happily test a patch to that file for you...the only box at my
house runs Windows... =-O
Ian Lance Taylor wrote:
Mark Mitchell [EMAIL PROTECTED] writes:
The new pex-win32.c code doesn't operate correctly when used for
MinGW-hosted tools invoked from a Cygwin window. In particular,
This is somewhat of a gcc-help@ question, but I'll try to help anyway :)
First, did cc1 just do this to you or can you reliably duplicate the
segfault? If you can't duplicate this error, it's probably a sign of a
hardware problem. If you can, then there's a bug in your host
compiler...which
I'm sorry about my e-mail client mangling your name in the To: field.
I don't know about the Microchip source, but I'd be happy to help with
the GCC-PIC18Fxxx port...however, PIC's have 1 true accumulator (W) and
everything else in data memory (which they use in the manner of a
register
Sounds like /bin/sh puked...What shell was that GCC configured with?
P.S. That looks to be a boehm-gc test that failed...which really
doesn't matter much (from an end-user perspective) unless you use GCJ...
David Fang wrote:
Hi all,
In reply to an earlier posting this month, from:
1) What would need to be done to reg-stack.c to allow other ports
besides i386 to use it? (support for multiple-stack machines would be
REALLY nice, but rather far off) (any other ideas?)
2) I found a minor bug in the header comment for reg-stack.c -- when
whoever wrote the comment
10 matches
Mail list logo
