Hello. I'm actually an EFI engineer so this project is of great
interest to me. I would be willing to lend a hand off hours if this
goes through, so please keep me in the loop.
I think the biggest hurdle would be the c front end since EBC (EFI
byte code) introduces variable sized pointers as wel
Hi,
I want to use the the wctype builtins ISWALPHA and the other ISW* functions to
handle the wide character string, but I get the following error:
/home/gcc/build/gcc/../../trunk/gcc/opts.c:1190: undefined reference to
`ISWALPHA'
collect2: ld returned 1 exist status
I have tried to grep som
On Thu, Mar 4, 2010 at 3:38 PM, Jean Christophe Beyler
wrote:
> Yeah that's what I had tried first but I get :
>
> genextract: Internal error: abort in VEC_safe_set_locstr
>
> And I can't seem to get rid of that error.
>
> Any idea why this happens?
Oh because the second time for the match_operan
Yeah that's what I had tried first but I get :
genextract: Internal error: abort in VEC_safe_set_locstr
And I can't seem to get rid of that error.
Any idea why this happens?
Jc
On Thu, Mar 4, 2010 at 6:28 PM, Andrew Pinski wrote:
> Maybe try this:
>
> (define_insn "myInst"
> [
> (set (match_
Maybe try this:
(define_insn "myInst"
[
(set (match_operand:DI 0 "register_operand" "=r")
(unspec:DI [(match_operand:DI 1 "register_operand" "r")
(match_operand:DI 2 "register_operand" "r")
(reg:DI 66)] 5))
(set (reg:DI 66)
(unspec:DI [(match_operand:DI 1 "register_operand" "r")
(match_o
Dear all,
I've been trying to define this instruction but am having
difficulties. This instruction does 3 things:
- Updates an internal accumulator (depending on two arguments)
- Returns the value of that update in an output register
- Updates the internal accumulator after that
I first wrote
Snapshot gcc-4.5-20100304 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.5-20100304/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.5 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk
引述 Andrew Haley :
There is no reason in principle this shouldn't be part of gcc.
I think no-one has responded yet because they don't know what it would
be for, and how much work it would involve.
What compiler doing is: c -> intermediate language -> asm(ex. x86).
And then, c compiler for efi
Dear all,
Although I probably shouldn't have been so harsh calling this
"mis-compiling", do you see any chance of back-porting this warning back
into the mainline?
P.S. The rationale of this exercise is of course that the "switch",
being a goto in disguise needs careful attention, just like th
