http://bugzilla.gdcproject.org/show_bug.cgi?id=94
Bug #: 94
Summary: ICE in bootstrapping with gcc HEAD
Classification: Unclassified
Product: GDC
Version: development
Platform: x86_64
OS/Version: Linux
Status: NEW
"Mike" wrote in message news:lxusmgyievzioacmg...@forum.dlang.org...
What bothers me is the branch at . It looks like it's checking the
struct instance to see if it is null. Is it even possible for it to be
null? Can this be improved?
It's checking if the 'this' pointer is null. Syntactical
I'm beginning to implement structs in my ARM Cortex-M runtime,
and I ran across something interesting today.
Consider this struct:
struct TestStruct
{
uint TestVar;
void Print()
{
trace.WriteLine("TestStruct.Print");
}
}
And a function that uses that struct:
void MyFunc
Am Fri, 24 Jan 2014 11:12:36 +
schrieb "Mike" :
> That appears to be it. I added memory to the clobber list and it
> worked without any extra modifiers. And, my executable is now
> only 56 bytes. It still doesn't do anything useful, but it's
> small and optimized :-)
>
> Thanks so much
On Thursday, 23 January 2014 at 16:56:19 UTC, Johannes Pfau wrote:
I think what could be happening here is that GCC doesn't know
what
memory you're accessing via the message pointer in SendCommand.
See http://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html
and search for "If your assembler instruc
