>> Here is a patch that tweaks it to use separate static CString buffer
>Don't helped.
Fixed on [mob]. Please verify.
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
> Here is a patch that tweaks it to use separate static CString buffer
Don't helped.
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Hello Michael,
I committed the revert. Based on what I see at the gitweb for the mob
branch (http://repo.or.cz/tinycc.git/shortlog/refs/heads/mob), it's not
there. I don't see anything between Vlad's commit and the one you pushed an
hour ago.
David
On Fri, Apr 22, 2016 at 9:43 AM, Michael Matz
Hello David,
On Mon, 18 Apr 2016, David Mertens wrote:
> I have nuked that commit.
Thank you for that. (But you haven't yet committed the revert, right?)
> For time management reasons, my recreational programming goes through a
> distinct email account, one that I hadn't checked since early
Hi,
On Wed, 20 Apr 2016, Sergey Korshunoff wrote:
> > Just checked. I used a hex editor to replace a 0x20 bytes in mem-2.o with
> > 0x04.
> > This helped.
>
> diff --git a/libtcc.c b/libtcc.c
> index 5aebd32..a8e109c 100644
> --- a/libtcc.c
> +++ b/libtcc.c
> @@ -514,7 +514,11 @@ ST_FUNC
> In any event, it is odd to me that any software compiled entirely from source
> should care about this sort of alignment. It should leave such issues up to
> the compiler, as an implementation detail, shouldn't it?
In the source code we can ask about a section where to place result,
an
