Ouch!You're fast, maybe too fast.I've no responsibility on tcc project. If I
think moving code to src is a good idea, it is my personal opinion. Official
maintainers may have a different opinion or want to choose different code
organization.
Anyway, here is what I can already say (from my RPi)-
On Mon, Jul 27, 2015 at 12:48 PM, Christian JULLIEN wrote:
> Hi Gus,
>
> This is a good idea. If you do so, I also suggest an arch directory that
> contains subdirectories for all supported archives
I wound up going with one dir per arch rather than an "arch"
directory. Let me know if there are a
I've not yet been able to build tcc on cygwin, neither in the
unix context provided by cygwin, nor with the --enable-cygwin
option which is out of date with the gcc naming schemes for
the mingw compilers on cygwin.
On Mon, Jul 27, 2015 at 12:48 PM, Christian JULLIEN
wrote:
> Hi Gus,
>
> This is
Hi Gus,
This is a good idea. If you do so, I also suggest an arch directory that
contains subdirectories for all supported archives
arch/armarch/arm64arch/i386...
I'm afraid this code refactory will take long until it works on all platforms
(including Windows).
Talking about Windows, who has a go
Hi,
ATM the root directory of TinyCC is a bit cluttered, mostly because
the core of TinyCC's code is there. I propose moving it to a "src"
subdirectory.
-gus
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinf
Hey Michael,
You are right about my type, I meant to say "int btype = type_to_check.t &
VT_BTYPE;"
Thanks for the confirmation, I'll start digging around elsewhere in my code.
David
On Mon, Jul 27, 2015 at 11:52 AM, Michael Matz wrote:
> Hi,
>
> On Mon, 27 Jul 2015, David Mertens wrote:
>
> >
Hi,
On Mon, 27 Jul 2015, David Mertens wrote:
> Hello everyone,
>
> While working on symbol table copying, I have run into trouble copying
> type.ref pointers that point to garbage. Suppose we have a type struct
> called "type_to_check". Then I thought the following check would ensure
> that the
Hello everyone,
While working on symbol table copying, I have run into trouble copying
type.ref pointers that point to garbage. Suppose we have a type struct
called "type_to_check". Then I thought the following check would ensure
that the .ref field was valid:
int btype = type_to_check->type.t &
Hello everyone,
I have been playing with symbol table copying and ran into some trouble
with uninitialized pointers. I figured my troubles arose because I didn't
fully understand the uses of Sym objects, so I thought I'd read through
tcc-doc. While reading I came across references to the .t field
