Re: Front end development question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



You should look at some of Andi's and my work
http://code.redbrain.co.uk/cgit.cgi/gccpy/ check out the 2 branches
gcalc and the documentation one. The gcalc front-end is a very simple
basic front-end with no frills. Or even check out gccpy or golang.
Fortran and Java front-ends are good when you start to get more
comfortable with front-end development.

Hope this helps. Looks like you may have some problems in your compiler driver.

--Phil

On 28 June 2012 19:18, Ian Lance Taylor <iant@xxxxxxxxxx> wrote:
> Josh Reese <jreeseue@xxxxxxxxx> writes:
>
>> Thanks for your prompt reply. I've tried running my driver the following ways:
>> ./gcc test.oas
>> ./goas test.oas
>> ./x86_64-apple-darwin11.4.0-goas test.'s
>>
>> As per your suggestion I have tried with -v but unfortunately this hasn't shed any light on the problem for me:
>> 11:21@legolas:.+4.7.0/local/bin$ ./gcc -v test.oas
>> Using built-in specs.
>> COLLECT_GCC=./gcc
>> COLLECT_LTO_WRAPPER=/Users/jreese/Documents/school/edinburgh/project/builds/oas-gcc4.7.0/local/libexec/gcc/x86_64-apple-darwin11.4.0/4.7.0/lto-wrapper
>> Target: x86_64-apple-darwin11.4.0
>> Configured with: ../srcdir/configure --prefix=/Users/jreese/Documents/school/edinburgh/project/builds/oas-gcc4.7.0/local --enable-languages=oas --disable-bootstrap
>> Thread model: posix
>> gcc version 4.7.0 (GCC)
>> COLLECT_GCC_OPTIONS='-mmacosx-version-min=10.7.4' '-v' '-mtune=core2'
>> /Users/jreese/Documents/school/edinburgh/project/builds/oas-gcc4.7.0/local/libexec/gcc/x86_64-apple-darwin11.4.0/4.7.0/./goas test.oas -o /var/folders/vt/hvgcc42n5md9_c94crkb1j9h0000gn/T//ccUJwJ7w.s
>> goas: error: vfork: Operation timed out
>>
>> (I've also done this for the other permutations of executing the driver…but it appears they are all doing the same thing in essence).
>> Is there something in this that perhaps makes sense to you? Thanks again for the reply.
>
> This does not make sense to me.  Sorry.  I think you are going to have
> to debug the driver program.  The error is most likely being generated
> in the function pex_unix_exec_child.
>
> Ian



[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux