patch pushed at
http://repo.or.cz/w/tinycc.git?a=commit;h=162e3a937c95cf1912a78d05ffef09b63ca02bd5
--- grischka
Sandor Zsolt wrote:
1. The tcc compiler can`t work with absolute defined include paths.
Solution: in tcc.c in function preprocess from the line 3063
/* now search in all
of it and have some Windows section
in tcc-doc.html, respectively extend what's already there:
(5.3 PE-i386 file generation)
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
lostgallifreyan wrote:
grischka gris...@gmx.de wrote:
(04/04/2009 16:40)
As people seem consequently to ignore what's called readme.txt,
meybe we should just get rid of it and have some Windows section
in tcc-doc.html, respectively extend what's already there:
(5.3 PE-i386 file generation)
I
lostgallifreyan wrote:
grischka gris...@gmx.de wrote:
No, I don't trust you. I just type
tcc hello_win.c
and it works. Why should we recommend horrible stuff like
DOS path and quoted full long name paths to newcomers?
Because that is what works in Windows. If it shouldn't be said
press another key to try out and run the result.
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
fsw...@comcast.net wrote:
Hello,
Looking at the libtcc.h file libtcc should be able to compile to an
output file instead of memory.
Wanted to experiment using libtcc.dll as a backend for another program.
With anything I try I get several errors, the file /usr/lib/crtn.o was
not found etc.
fsw...@comcast.net wrote:
Thank you very much for your help.
Got the newest files from git (...manually - have problems with
tortoise-git)
Manually? There are links for snapshots (.zip / .tar.gz) on
http://repo.or.cz/w/tinycc.git
but tcc doesn't compile, it says:
tcc: undefined
fsw.fb wrote:
grischka wrote:
fsw...@comcast.net wrote:
Thank you very much for your help.
Got the newest files from git (...manually - have problems with
tortoise-git)
Manually? There are links for snapshots (.zip / .tar.gz) on
http://repo.or.cz/w/tinycc.git
The problem
stop windows users from asking why they
can't type TCC FILE.C, I'm afraid.
--- grischka
--Ivo
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
://repo.or.cz/w/tinycc.git?a=shortlog;h=92c58361
Links to shapsnots are at the rightmost end of the lines.
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
lostgallifreyan wrote:
Joshua Phillips jp.sittingd...@gmail.com wrote:
(15/04/2009 13:46)
stricmp or strcasecmp would be provided by the C library. Tcc is only a
compiler - it doesn't include a C library. Therefore, the presence of stricmp
or strcasecmp will be determined by the C library
While I was in refactoring mood I created 4 new files:
tcc.h
tccpp.c
tccgen.c
tccmain.c
That is tcc.c split into parts.
http://repo.or.cz/w/tinycc.git?a=shortlog;h=35bb7a93
Do we want this?
--- grischka
by linking
tccmain.o with libtcc.a (.so/.dll).
We could rename tcc.c to libtcc.c and tccmain.c to tcc.c. It would
make sense, just then tcc.c would #include libtcc.h, while libtcc.c
would #include tcc.h, unless we rename tcc.h to something else.
On Mon, Apr 20, 2009 at 5:20 AM, grischka gris
So I renamed tcc.c to libtcc.c and tccmain.c to tcc.c.
Such that now more intuitively libtcc is made from libtcc.c
and tcc is made from tcc.c.
http://repo.or.cz/w/tinycc.git?a=shortlog;h=bf4a40f504bd78380d10a1529bdd9b58a985f252
How looks that?
--- grischka
grischka wrote:
While I
at it. The TCC_MAIN is just to keep the code
logically identical to how it was before the split. Of course
this can go away later.
--- grischka
On Mon, Apr 27, 2009 at 6:01 AM, grischka gris...@gmx.de
mailto:gris...@gmx.de wrote:
So I renamed tcc.c to libtcc.c and tccmain.c to tcc.c.
Such that now
;i++)
for(k=j+4;k13+i;i++)
if((v(a[i]|a[j]|a[k]))==v) {
...
for(i=0;i8;i++)
for(j=i+4;i12;i++)
for(k=j+4;k13+i;i++)
if((nv(a[i]|a[j]|a[k]))==nv) {
which looks like it could be typos. Daniel?
--- grischka
I have put together a release candidate for 0.9.25:
http://repo.or.cz/w/tinycc.git
which I plan to upload at savannah in a week or so. Say unless
there is something important still missing.
--- grischka
___
Tinycc-devel mailing list
Tinycc
Stefan de Konink wrote:
grischka wrote:
Does this work:
http://repo.or.cz/w/tinycc.git?a=commitdiff;h=41530212587759831141f993e80fdbcd263e4c72
It does! I think you should announce this on the uclibc list for the
next release too :) :)
Maybe you can do that? ;)
I don't know if the 64bit
Stefan de Konink wrote:
Stefan de Konink wrote:
grischka wrote:
I have put together a release candidate for 0.9.25:
http://repo.or.cz/w/tinycc.git
which I plan to upload at savannah in a week or so. Say unless
there is something important still missing.
I think getting any
vijay mohan wrote:
Hello,
Is it possible to use the run option with static libraries. ie
something like
tcc -run test.c -lStr
where Str is a library called(say) LibStr.a created with tiny_libmaker.
Yes, just put any options *before* -run. Like
$ tcc -lStr -Istuff ... -run test.c
demangle_component comps[di.num_comps];
__extension__ struct demangle_component *subs[di.num_subs];
#else
???
I figure there is maybe code for compilers that don't have dynamic
arrays. There are some C99 extensions in TinyCC, just not this
one (yet?).
--- grischka
), there are some differences with calling convention,
one being that it uses only 4 register for arguments (RDX, RCX, R8, R9)
-- http://msdn.microsoft.com/en-us/library/ms235286.aspx
However don't worry now.
--- grischka
___
Tinycc-devel mailing list
able to find.
Of course we cannot be sure that this was the only implication
however I'd suggest to apply your patch now and worry later.
As always, you can push patches on our mob branch:
$ git push ssh://m...@repo.or.cz/srv/git/tinycc.git mob:mob
--- grischka
There are two places where
have/use AV programs.
--- grischka
\tcc\tcc hello_dll.c -L\tcc\examples -ldll
I get the worm warning:
Email-Worm.Win32.Zhelatin.uq was found in W:\tcc\examples\hello_dll.exe on
10.06.2009 09:59:44
Since I don't know which AV programs my future users will have, I can't
use tcc for my actual
-b is meant to be used with -run where tcc prints
__bound_error_msg from its built-in exception handler:
$ tcc -b -run outofbound.c
You can also try the btest example, which runs the snippets in
tests/boundtest.c:
$ make -C tests btest
--- grischka
interface.
For now TCC's only input is C and the only in memory representation
is machine code.
See libtcc.h for the interface and tests/libtcc_test.c for an
usage example.
--- grischka
It is very likely that this project becomes our primary focus for the
time to come so we're very interested
compiler as well, of course. Including the capability
to run the code JIT or to write out executables for linux and windows.
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
Simon Lehmayr wrote:
Hello,
is there a way to compile a windows dll with tcc?
tcc -shared file.c
See tcc-win32.txt and the hello_dll example.
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
Sam Watkins wrote:
I switched to the mob branch and commited it locally, but the push
fails:
$ git push
fatal: unexpected EOF
git push ssh://m...@repo.or.cz/srv/git/tinycc.git mob:mob
This means:
git push repo-address local-branch:remote-branch
Maybe you can configure it such that
familiar with LibJit?
I can see how it compiles to run, but how save the code to file?
Or add external references and relocation entries?
Looking at this:
http://www.gnu.org/software/dotgnu/libjit-doc/libjit.html
--- grischka
___
Tinycc-devel
?a=commitdiff;h=dd37d7b5
?
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
Andrea Fazzi wrote:
Hi all,
I wonder if is planned a fix for the issue described in the first
part of the post below:
http://lists.gnu.org/archive/html/tinycc-devel/2007-04/msg7.html
I'm developing a ruby binding for libtcc and I've got the same issue with
the error symbol. Fixing the
Simon Lehmayr wrote:
Hi,
I found an error in tcc while compiling a project which uses one header
that includes another header several times using defines to generate
different code.
Caching of headers hides the following includes thus no code is
generated in these cases.
I disabled caching
Jerome Vuarand wrote:
2009/5/20 grischka gris...@gmx.de:
Changes:
- [...]
- tcc_relocate now copies code into user buffer
- [...]
I'm in the process of updating a program that links to libtcc, and
this change is quite annoying. It would have been nice to keep the old
tcc_relocate as-is (put
?
Was a similar functionality integrated yet?
The question was just whether that alternative patch would suit your purpose
(i.e. prevent further frustration ;))
To get a snapshot click on shortlog and then on snapshot (tar.gz zip)
in the related line.
.
--- grischka
to suppress
this warning (and many more of the same kind). Why doesn't it work for you?
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
was necessary to support 64-bit targets.)
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
compiler to build tcc.exe as cross compiler
(but then you can't use the -run feature).
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
Floris Bos wrote:
Altough tcc itself compiles, building libtcc1-x64 fails:
==
.\tcc -o tmp.s -E ../lib/alloca86.S
yasm -p gnu -f elf64 -o alloca86.o tmp.s
tmp.s:8: error: invalid size for operand 1
Something got out of sync. It needs to be libtcc1.a
(without -x64), and alloca86_64.
branch?
Some questions:
- is the rename from IMAGE_ to PECOFF_ really necessary?
- can you preserve the directory structure?
- can you split the changes into separate commits, say one
for 16-bit assembly, one for x86_64, and so on. (not a big
deal but would be nice)
Thanks,
--- grischka
on. (not a big
deal but would be nice)
Thanks,
--- grischka
Hi grischka,
I use TCC to compile TCC. I tried to compile it with PE support under
Windows, and I
obtained some error messages, due to a conflict with the IMAGE_*
structures defined in winnt.h.
So, I renamed IMAGE_* to PECOFF_
problems to assemble
its own __chkstk function. In particular there are some 66 prefixes that should
not be there. See below.
Mr. Frederic Feret, would you look into it ?
Thanks,
--- grischka
004010A0 66:872C24 xchg [esp],bp
004010A4 55push ebp
004010A5 66
=e90c6f21a89257c8b6e5f396444068e685c1a9e3
I know there are more than one person out there who should be able to fix this, I
just hope it happens ;)
--- grischka
- Original Message -
From: Rutenis Turcinas rutenisturci...@gmail.com
To: tinycc-devel@nongnu.org
Sent: Wednesday, October 28, 2009 12
Hi, when compiling using GCC the function gets exported as it's named (well,
mangled) but then compiling with TCC its name has an underscore before it:
__declspec(dllexport) LRESULT CALLBACK LowLevelHook(int nCode, WPARAM
wParam, LPARAM lParam)
If GCC it's lowlevelh...@12, TCC makes it
you use.
Is there any
solution on how to compile a program which makes use of any of these calls?
Write them. Or get some source code. (I guess there should be some
in the mingw-runtime-xxx-src pack)
--- grischka
Thanks you very much.
___
Tinycc
};
Indeed, there is a missing flcose(op).
I have fixed the leak and attached the file to this mail.
Thanks. Committed to
http://repo.or.cz/w/tinycc.git/commitdiff/cbd7f29e
Please consider sending patches or pushing to our mob branch
directly, next time ;)
--- grischka
Best regards
Martin
, download the package, open with say 7-zip, copy the files
from include into your tcc/include/winapi, and hope that it
works.
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
Thanks Jörg.
A note to everybody: Be aware that if you configure git with
your real email address it will be visible on the web interface.
--- grischka
Jörg Mische wrote:
Hi all,
I found a small bug when storing structures in vstore(): the store is done by a
call to memcpy
on old tcc-0.9.25. Otherwise nobody will have
time to resolve the merge conflicts.
See: http://repo.or.cz/w/tinycc.git
(There are links to download tar balls for each revision)
Even better if you could push your patches on our mob branch directly.
--- grischka
Hope people will find it useful
. Also I created a new branch
mob-stuff where I stacked some stuff from previous mob that I
don't know what exactly to do with it, at the moment.
Regards,
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman
) {)
- Get it back from a typedef symbol into the attribute
(that is in parse_btype() at line typedef_found = 1;)
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
might help to find out at least.
--- grischka
Regards.
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
(TCCState s, const char *option_string);
Which then could be use like:
tcc_set_options(s, -nostdlib -lsqlite -w -);
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
of cross reference of the functions and variables, so you already
(almost) have the prototypes. (See notes in the commit how to use it)
--- grischka
Regards, K1w1.
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman
bounds checking on windows currently.
I don't say it is not possible but it will not work out of the
box.
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
Christian Jullien wrote:
Q. how can I see the .s output (as generally using -S on most compilers) ?
TCC outputs machine code, not assembler.
You can disassemble it though:
$ tcc -c x.c
$ objdump -D x.o
on win64:
$ x86_64-pc-mingw32-objdump -D x.o
--- grischka
. Because nobody wants to fix
the same bugs twice.
Regards, k1w1.
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
representation that tcc does not have.
It's not that I don't like the idea.
---grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
procedures, threads and some such.
--- grischka
#include stdio.h
#include stdlib.h
#include setjmp.h
int
main(int argc, char *argv[])
{
jmp_buf buf;
if (setjmp(buf) == 0) {
printf(ready to jump at %p\n, buf);
longjmp(buf, 1);
printf
://repo.or.cz/w/tinycc.git/commitdiff/a98caba0
--- grischka
Could you please review the patch?
} else {
if (op == TOK_UDIV || op == TOK_UMOD) {
#if 1
if ((vtop-type.t VT_BTYPE) VT_LLONG) {
o(0x9948); /* cqto */
o
in current master branch.
http://repo.or.cz/w/tinycc.git
Commit patches (if any) directly on our mob branch. Thanks,
--- grischka
Dwight
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
. Is it possible that
TinyCC is simply compiling the function call with a 32-bit instructon?
master version is here:
http://repo.or.cz/w/tinycc.git
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman
headers (such as stat32/64).
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
would use incompatible
calling convention to functions added using tcc_add_symbol.
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
is another idea. You could actually just declare the
function(s) as dllexport and then add the program itself using
tcc_add_file. It would then use it's own IAT (import address
table) as jump table.
--- grischka
#include stdio.h
#include libtcc.h
__declspec(dllexport) void print (const char
and large distance calls on win64 (as
pointed out recently by Michael Kuklinski)
* Usage of r8/r9 as load/store registers on x86_64
* ...
See http://repo.or.cz/w/tinycc.git
Happy new year,
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel
:1983).
Is this desired behavior?
Can you show that memory waste actually happens in practice? Say if
you'd load the same .so 1000 times?
--- grischka
Thanks,
Joey
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org
0;
}
For those who like to play with it, I attached the test cases in a more
runnable form. (run tcc -D T1..17 -run bugs.c)
--- grischka
#include stdio.h
#include stdlib.h
int my_assert(const char *msg, const char *file, int line)
{
fprintf(stderr, %s:%d: error: assert (%s)\n, file, line
a different notion of this (that
is the same as tcc, currently) but I think we are safe to assume that
gcc is right ;)
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
: error: ';' expected
There are also some warnings about macro redefinitions but didn't break
the build.
Thanks. I fixed it on the mob branch.
--- grischka
My platform right now is a 32-bit Win7 Professional, with w32api package
version 3.14. TCC was built using a development build of GCC
.
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
at
http://repo.or.cz/w/tinycc.git
Merci,
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
://msdn.microsoft.com/en-us/library/zthk2dkh.aspx
Do not expect me personally to fix this.
--- grischka
Gabor Gyorgy Nagy n...@freemail.hu írta:
Hi list,
seek.c:
#include windows.h
#include stdio.h
#define O_RFLAG GENERIC_READ, FILE_SHARE_READ, NULL
. Is there any possibility,
a patch or is this a feature, which is planned?
What do you mean by tcc obviously has no UNICODE support?
I mean you can take hello_win.c, put #define UNICODE on top, make
some trivial changes and it works. What would you need more?
--- grischka
the GOT after linking (only for x86-64).
Ali
Please push patches on our mob branch:
http://repo.or.cz/w/tinycc.git
Thus it is also easier for other people to test and give you
feedback.
Thanks,
--- grischka
From: Ali Gholami Rudi a...@rudi.ir
Subject: [PATCH] fill got table
, so you still
need to use the -B switch. Patches to our mob branch are welcome, as
always ;)
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
correctly (and with i386-win32-tcc
installed) all you need (and ever should need) is:
$ cd win32/examples
$ i386-win32-tcc hello_win.c
This produces hello_win.exe that can be run on windows or under wine.
--- grischka
___
Tinycc-devel mailing list
Tinycc
/archive/html/tinycc-devel/2010-02/
Btw, please don't send patches to the list. Instead push them
directly on our mob branch.
http://repo.or.cz/w/tinycc.git
Thanks,
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http
-win32.txt:
Import Definition Files:
To link with Windows system DLLs, TCC uses import definition
files (.def) instead of libraries.
...
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http
Simon Lehmayr wrote:
Hi,
how can I setup tcc to compile and debug tcc itself with MS visual
studio 2005?
You want tcc do debug itself with MSVS?
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman
Simon Lehmayr wrote:
Hi grischka,
no, I want to compile tcc from its sources and debug tcc under MS visual
studio.
Just as always: Create a console project, add tcc.c, fiddle with
the build options, and hit F7.
Well, you'd also need to create a config.h (see build-tcc.bat).
--- grischka
complex, that I've overlooked?
Maybe not. As always, please push patches on our mob branch ;)
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
type.ref set. That's likely why it crashes
and wouldn't work anyway.
I know that the dllimport attribute works for data.
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
Please push this on mob.
--- grischka
Timo VJ Lähde wrote:
win32/tools/tiny_libmaker leaves temporary files on error
-
--- a/tiny_libmaker.c Mon Mar 15 23:51:00 2010
+++ b/tiny_libmaker.c Wed Mar 31 22:35:06 2010
@@ -99,6 +99,7
Timo VJ Lähde wrote:
No, but it makes possible to use _winstart as entrypoint directly
without runtime library.
You are repeating yourself.
--- grischka
- Original Message - From: grischka gris...@gmx.de
To: tinycc-devel@nongnu.org
Sent: Friday, April 02, 2010 12:43 PM
Subject: Re
,subsystem,xxx should override the smart logic with
WinMain. Also don't forget to check that tcc -run ... still
works.
Once you feel reasonably sure enough that you did the right thing,
please push your patch on our mob branch.
Thanks,
--- grischka
___
Tinycc
Timo VJ Lähde wrote:
If i compile tcc.exe with tcc.exe, i can't run it in WindowsXP because
of missing function in msvcrt.dll : ftime32().
--Timppa
Thanks. I've pushed a fix on mob.
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel
Timo VJ Lähde wrote:
Is that correct ?
tccpe.c 1824:
#if defined(TCC_TARGET_ARM)
pe.subsystem = 3;
#else
pe.subsystem = 9;
#endif
In WinCE ARM should be pe.subsystem = 9; ?
--Timppa
Looks wrong. Maybe it was meant to be
#if !defined(TCC_TARGET_ARM)
--- grischka
.
If I may propose something else then maybe you could just move the
default system path settings from tcc_new to tcc_set_output_type
(to where it happens for TCC_TARGET_PE) which is when the command
line was already parsed.
--- grischka
___
Tinycc
and also breaks
compilation of some older code I use for testing.
Could you provide me an example where this is the case ? (Cf my previous
answer)
Appears it was not an error in GCC 3.x but is one in GCC 4.x. Maybe
we could make it just a warning for now. Do what you want ;)
--- grischka
(filename));
dynarray_add((void ***) libs, nblibs, tcc_strdup(libname));
But then again I'm a perfectionist ;)
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
to mob
Then you should check that no one else has committed new patches
to the public mob in between.
And then you could replace the public mob with your new version,
using git push --force ...
BUT, you need to be careful not to mess up other peoples' work.
Thomas Preud'homme
--- grischka
other peoples' work.
Don't worry, I know all the consequences it could produce.
Great ;)
--- grischka
Thomas Preud'homme
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
.
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
Please use the tinycc mailing list:
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
Original Message
Date: Wed, 28 Apr 2010 17:18:09 +0300
From: Kirill Joss jos...@gmail.com
Hi !
Source code:
struct {
int DeviceID;
int StartAddr;
int
Detlef, please fix.
(Beware, not as suggested below ;))
--- grischka
Timo VJ Lähde wrote:
Maybe check first previous char if possible but using negative pointer
isn't safe:
tccpp.c line 2281
case '.':
/* check first for a local label (.Lxx:) */
if (p[1] == 'L' (p[-1] == '\n
Thomas Preud'homme wrote:
Hi all,
I'm sorry I made a little typo which made a huge error: it deleted the mob
branch.
Can happen.
I pushed my latest mob. I don't have a28b18fa though, so it's up to you
(or someone else) to push that and what's in between (if any).
--- grischka
Don't
to undefined memory
3) the feature (as in jmp .L0) would not work anymore
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
).
--- grischka
If it is building tcc1.def for you then you can use that I think.
Cross-compiling 32 bit windows programs (on Linux):
The problem with libtcc1.a (tcc1.def) is it is difficult to build
without windows because it contains ELF objects and so it is built with
32 bit version of i386-win32-tcc
mobi phil wrote:
On Sun, May 16, 2010 at 10:02 PM, grischka gris...@gmx.de wrote:
For bug reports please use latest mob or master branch from
http://repo.or.cz/w/tinycc.git
Thanks,
Did not mention it indeed, but this was tested on
git://repo.or.cz/tinycc.git, both master and mob.
Sorry
101 - 200 of 803 matches
Mail list logo
