David G. Koontz wrote:
Does a simple "hello world run" without the segmentation fault?
It wouldn't get elaborated without the compiler.
You seem to have missed the main point of my earlier message:
It looks like you're building an mcode target, which doesn't create
object files.
i.e., the GHDL you have built __IS NOT USING THE GCC BACK END__
It is instead using the mcode back end, which is a stand alone JIT
module that generates object code at runtime.
With the mcode back end, elaboration is redundant, and can be skipped.
See section 3.1.2 of the GHDL manual, but read "mcode" for "windows":
"
" On GNU/Linux the elaboration command creates an executable
" containing the code of the VHDL sources, the elaboration code
" and simulation code to execute a design hierarchy. On Windows
" this command elaborates the design but does not generate anything
"<snip>
" On Windows this command can be skipped because it is also done
" by the run command.
the GNAT 64 bit binaries don't run on my older mini with a "Core Duo"
CPU.
They should run under darwin9.6 or darwin10 environments (10.5.7 and
up if
memory serves). A Core 2 Duo is an x86_64 machine
"Core Duo", that I have at hand, is a 32 bit machine
"Core 2 Duo", with an extra '2', is 64 bit capable
------------
I think I have tracked down the Windows mcode stack allocation bug,
with a fix better than the double-the-stack-alignment-constant hack
I mentioned earlier; I'll post a patch in a day or so once I've run it
against some non-trivial VHDL source code.
That same bug might be causing your OS-X mcode segmentation fault.
Brian
_______________________________________________
Ghdl-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/ghdl-discuss
