gt;> But this is a very huge task to make it work. Until then, I'll continue to
>> use my Makefile on Cygwin which is close to my ideal.
>>
>> Christian
>>
>>
>> -Original Message-
>> From: Tinycc-devel
>> [mailto:tinycc-devel-bounces+eligis=ora
se, I look
forward to contributing development of
a native posix cygwin tcc.
--Chris
On 10/11/2017 19:14, Chris Marshall wrote:
I was able to 'make' and 'make test' with
the original win32/Makefile. I got home and
tried the "new" version building with cygwin
and now it
I was able to 'make' and 'make test' with
the original win32/Makefile. I got home and
tried the "new" version building with cygwin
and now it doesn't pass tests because it says
-run is not valid for a cross compiler.
I think this is a bug since tcc does not
have a posix version for cygwin so whi
I would like to have the ability to contribute to
tcc in a more structured fashion. I have been working
to get tcc to build/run on cygwin but only in private work.
Without a way to publicly contribute to tcc development
I have little hope of having other contributers to assist
with the cygwin wo
Thanks for the quick reply. Maybe the patch could be the start of a
topic branch to port tcc to cygwin at some point. Best wishes with the
release.
--Chris
On 10/10/2016 13:23, grischka wrote:
Chris Marshall wrote:
Attached is a patch to the current mob which
allows cygwin to be correctly
part of the planned tcc
release will increase chances of having things
work on cygwin eventually.
Thanks much,
Chris
From b12af2cd171f26b1a41afcc9866918d0ae214abf Mon Sep 17 00:00:00 2001
From: Chris Marshall
Date: Fri, 20 May 2016 08:02:03 -0400
Subject: [PATCH] Basic port to cygwin of mob tcc
debug the problems of the
cygwin system includes for gcc to use as simply as possible with tcc
compilation?
--Chris
Second:
On 5/20/2016 11:10, Chris Marshall wrote:
Gives me the clue that the problem may be in the parsing rather the pp
stuff.
The output when PARSE_DEBUG is set definitely
, May 20, 2016 at 11:02 AM, Chris Marshall
wrote:
> Hi David-
>
> Ack! I was only looking at the tccpp.c since the problem was with the
> includes.
>
> I think if you select the Devel all you'll get alot of things which should
> be enough.
> Off the top of my head,
nstallation, which Cygwin packages would I need to install to get to where
> you are?
>
> David
>
> On Fri, May 20, 2016 at 8:24 AM, Chris Marshall
> wrote:
>
>> Atttached is a first cut port of the TinyCC build to the cygwin platform.
>>
>> The mains problems
4157c9927cb3706f4e902ae88710 Mon Sep 17 00:00:00 2001
From: Chris Marshall
Date: Fri, 20 May 2016 08:02:03 -0400
Subject: [PATCH] Basic port to cygwin of mob tcc
The remaining issues appear to be ones relating to include file
problems. Specifically, the local include/stddef.h and others
seem to be i
thing is off-by-one or something.
Will try the current git mob next.
--Chris
On Thu, May 19, 2016 at 1:49 PM, Chris Marshall
wrote:
> Is it possible that this could be a bug in the tcc preprocessing?
>
> On Thu, May 19, 2016 at 10:33 AM, Chris Marshall
> wrote:
>
>> Tha
Is it possible that this could be a bug in the tcc preprocessing?
On Thu, May 19, 2016 at 10:33 AM, Chris Marshall
wrote:
> Thanks for the help.
>
> I've got tcc building but the bcheck.c compile is failing
> when the stdlib.h is pulled in. My next step is to try
> the same
I'm working to port the tcc build process to cygwin
and its native posix environment. tcc.exe seems to
build fine but I'm having include problems with the
compilation of lib/bcheck.c.
Is there any way to see exactly what is generated
in the failing include files with command line switches
or othe
Thanks for the help.
I've got tcc building but the bcheck.c compile is failing
when the stdlib.h is pulled in. My next step is to try
the same with the latest tcc git. I'm not sure what the
best way to proceed woud be. The top level gcc build
can correctly (for cygwin) process the various syste
ere is a link to the work done in cygwin to overlay the ucontext structure
so it refers to the underlying windows locations:
https://cygwin.com/ml/cygwin-cvs/2015-q2/msg00141.html
--Chris
On Mon, May 16, 2016 at 10:44 PM, David Mertens
wrote:
> On Sat, May 14, 2016 at 3:27 PM, grischka
by tcc the __CYGWIN__ macro is not defined
and I can't figure out where that would go.
At that point things build but the tests fail because crt1.o, crti.o and
crtn.o
are not correctly located.
--Chris
On Tue, May 17, 2016 at 3:42 PM, Chris Marshall
wrote:
> I don't mean exactly t
To be more specific, it should be possible to build the mingw version of
tcc on cygwin (I don't know, haven't had time to try) but what I would
like is the linux/unix version---if it builds on unix, it should be
buildable on cygwin---as long as you don't look under the covers to find
windows.
As someone whose primary development environment is cygwin/win7, I would
love for tcc to build and run under cygwin.
--Chris
On 5/14/2016 03:24, Sergey Korshunoff wrote:
MSYS2 is current environment for Qt and other software development on
Windows. It is a mingw+cygwin with a package manager
The problem isn't that BytesWritten is not a pointer, it
is that you don't have it pointing to any valid location
which is why the crash in WriteFile().
--Chris
On 1/10/2016 07:31, Ben Hutchinson wrote:
When I try to compile this:
#include
int _start(void){
unsigned char MyArray[4];
LP
Thanks for the reply, Edmund.
The main thing I was looking for was support
for complex arithmetic in expressions with
+, -, *, and /. Anything in function call form
can be readily implemented by hand.
Regards,
Chris
On 11/18/2015 06:53, Edmund Grimley Evans wrote:
I'm currently working on so
I'm currently working on some experiments to
use tinycc as a JIT compiler for the computational
code for a portable numeric library (the Perl
Data Language, http://pdl.perl.org).
We have a requirement to support computation
with complex numbers and arithmetic (C99).
The initial developments look
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
onsult the file "CYGWIN_LICENSE" for
> details. */
>
> #ifndef _SYS_UCONTEXT_H_
> #define _SYS_UCONTEXT_H_
>
> #include
>
> typedef struct __mcontext mcontext_t;
>
> typedef __attribute__ ((aligned (16))) struct __ucontext {
> mcontext_t uc_mcontext;
&
Hi David-
I'm just coming up to speed initially which is why I was interested
in just how far tcc could go. I agree that a perl compiled with tcc
is probably not useful.
I definitely plan to look at the C::TinyCompiler and XS::TCC
modules once I can get tcc and libtcc running on my cygwin
setup.
On Thu, Jul 16, 2015 at 7:21 PM, Jared Maddox
wrote:
> >
> > http://ldeniau.web.cern.ch/ldeniau/cos.html
> > https://github.com/CObjectSystem/COS
> >
> > The features and capability look very good and I believe
> > will be sufficient for PDL development save the fact that
> > it apparently do
I would like to integrate tcc with some perl5 programs to the best extent
possible.
Has anyone tried and/or reported being able to build perl5 with tcc?
Thanks,
Chris
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/
On Thu, Jul 16, 2015 at 11:06 AM, wrote:
> On Thu, Jul 16, 2015 at 09:38:04AM -0400, Chris Marshall wrote:
> > I'm new to the tcc-devel list but the thread last month at
> >
> >
> http://lists.nongnu.org/archive/html/tinycc-devel/2015-06/msg2.html
>
> >
I notice in the tcc-0.9.26 TODO file that C99 complex number
support is not present. Has there been any further work to
support complex arithmetic and/or what the required level of
effort would be?
Thanks,
Chris
___
Tinycc-devel mailing list
Tinycc-deve
I'm new to the tcc-devel list but the thread last month at
http://lists.nongnu.org/archive/html/tinycc-devel/2015-06/msg2.html
is directly relevant to my interest in tcc which is to enable
JIT computing to the Perl Data Language along with a new,
symmetric framework for computation so that
29 matches
Mail list logo