Le vendredi 27 août 2010 12:47:35, Aharon Robbins a écrit :
> Hi. I've reported this before, but here is a small test case:
>
> $ cat foo.c
> #include
>
> static void func();
>
> int main(int argc, char **argv)
> {
> static struct s {
> void (*elem)();
> } t[] = {
>
31ca000d72bc48060f205d94bfffc25ffe5fd18d
Best regards.
Thomas Preud'homme
signature.asc
Description: This is a digitally signed message part.
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Le mardi 5 juillet 2011 19:04:22, grischka a écrit :
> Thomas Preud'homme wrote:
> > #ifdef CONFIG_TCC_EXTRA_LDDIR
> >
> > {
> >
> > const char delim[] = ":";
> > char *tok, *tok_extra_libdir = NULL, *tok_save
Le jeudi 7 juillet 2011 07:39:10, Christian Jullien a écrit :
> Or even better:
>
> #!/usr/bin/env tcc -run
Sure
>
> -Original Message-
> From: tinycc-devel-bounces+eligis=orange...@nongnu.org
> [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of
> grischka
> Sent: jeud
Le jeudi 7 juillet 2011 10:23:52, Thomas Preud'homme a écrit :
> Le jeudi 7 juillet 2011 07:39:10, Christian Jullien a écrit :
> > Or even better:
> >
> > #!/usr/bin/env tcc -run
>
> Sure
Done, see commits 4d6a4a2..27a428c.
>
> > -Original Message--
Le jeudi 7 juillet 2011 00:06:37, grischka a écrit :
> Thomas Preud'homme wrote:
> >> Also, I'd claim that using strtok is somehow un-tcc'ish, seen that
> >> there are zero occurrences anywhere else. ;)
> >
> > Ah. Then what tcc'ish functi
Le jeudi 7 juillet 2011 20:22:30, vous avez écrit :
> Thomas Preud'homme wrote:
> > And also sorry for introducing so stupid bugs.
>
> It was not your fault, it is all strtok's fault. ;)
>
> As to the new version:
>
> - I don't seem to like my
t can be tried with multilib subdir. So all
what would be needed is to split paths in two variables and change the
functions using it, eg. library_paths would become system_library_paths and
user_library_paths and tcc_add_library would then use both these dynarray
differently. Same for other sear
Le vendredi 8 juillet 2011 18:42:01, Thomas Preud'homme a écrit :
[SNIP]
>
> === Sketch for a (hopefully) better solution ===
>
> One thing to remember though is that almost all files (headers, object,
> archive, but not ld.so) are included via
> tcc_add_file_internal(s1
Le samedi 9 juillet 2011 20:44:47, grischka a écrit :
> Thomas Preud'homme wrote:
> > First let's focus on multilib as you said.
>
> Actually I said "multilib" because you said "multilib". Which
> means that I've no idea really what it means.
Le dimanche 10 juillet 2011 18:05:57, grischka a écrit :
> Thomas Preud'homme wrote:
> > I wrote the code yesterday. Please take a look. Still missing is the
> > handling of elf_interp but this must be added anyway without this
> > option.
>
> Well, to me the be
/stdlib/strtold.c?id=ed3d3458eff834d82b01f4018f7750fba1449a07
So the question is: do we still need to define them for these platform in
tcc.h? If yes, we need to be more specific and say for which version they must
be defined.
Best regards,
Thomas Preud'homme
signature.asc
Description: This
Which version of the package do you use (what gives you dpkg -l tcc)?
[SNIP]
>
>
> Greetings Thomas Mertes
Thanks for your interest in tinycc.
Best regards,
Thomas Preud'homme
signature.asc
Description: This is a digitally signed message part.
y
problem, please fill a bug report (against Debian or Ubuntu as you prefer).
>
>
> Greetings Thomas Mertes
Best regards,
Thomas Preud'homme
signature.asc
Description: This is a digitally signed message part.
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Le dimanche 31 juillet 2011 15:58:25, grischka a écrit :
> Thomas Preud'homme wrote in
> http://repo.or.cz/w/tinycc.git/commitdiff/b2f5ee9b2d
>
> > Force const. expr. in expr_cond outside function
> >
> > Since no code should be generated outside a function, forc
Le dimanche 31 juillet 2011 16:27:57, grischka a écrit :
> Thomas Preud'homme wrote:
> >> Can you show an example where this happens, that is that
> >>
> >> const_wanted is false
> >>
> >> and
> >>
> >> cur_text_se
Le dimanche 31 juillet 2011 17:23:28, grischka a écrit :
> Thomas Preud'homme wrote:
> > Mmmmh good point, I should have tried with mob. I can't reproduce it
> > neither. So I guess master is not as close to mob as I thought.
>
> Plus running the const_wanted br
Le dimanche 31 juillet 2011 18:48:04, grischka a écrit :
> Thomas Preud'homme wrote:
> >> Plus running the const_wanted branch without const_wanted being
> >> actually set doesn't look like a good idea. It could still
> >> generate code in the gen_cast()
Le lundi 1 août 2011 01:24:56, Michael B. Smith a écrit :
> Are those semicolon strings on Windows?
Yes they are: colon on UNIXes and semicolon on Windows. Look at the definition
of PATHSEP in tcc.h (should be line 872 to 876).
Best regards,
Thomas Preud'homme
>
> -Or
Le lundi 1 août 2011 01:19:54, grischka a écrit :
> Thomas Preud'homme wrote:
> > I knew you would answer something like this. That's why I didn't apply
> > the patch straight forward.
>
> You did not apply the patch because you knew it doesn't work? ;
Le lundi 1 août 2011 19:22:19, grischka a écrit :
> Thomas Preud'homme wrote:
> > Solution 1:
> Yes. Good luck ;)
Done (see 76adc57). I have a "solution" for the elf_interpreter in Debian but
it's more invasive (~10 lines of code added) and only suited for nat
and make a tar of it. I guess ttylinux contains tar.
Other solution would be to build it yourself and then make a tar of it.
Best regards,
Thomas Preud'homme
signature.asc
Description: This is a digitally signed message part.
___
Tinycc-devel ma
Le mercredi 3 août 2011 18:59:04, grischka a écrit :
> Thomas Preud'homme wrote:
> > Done (see 76adc57). I have a "solution" for the elf_interpreter in Debian
> > but it's more invasive (~10 lines of code added) and only suited for
> > native compilers (
Le mercredi 3 août 2011 19:36:47, grischka a écrit :
> Thomas Preud'homme wrote:
> >> Why is it necessary to look in two directories at runtime for
> >> elf_interp and for the crt objects?
> >
> > Actually I realized only today how big mistake it was for the
t; Unquoted strings. Hm...
Commit reverted. I tried with dash and it worked but it seems the
expansion/escaping rules are different between dash and bash when both run as
/bin/sh. Anyway, this commit had to be reverted.
Sorry for the breakage.
Best regards,
Thomas Preud'homme
>
> Looks li
ault ./global_affect
I might be completely wrong but I have the impression that the problem is that
when a symbol value is made pointer, its constant value is not set to its
address. As init_putv assume the symbol value pointed at by vtop has a correct
constant, it fails.
Best regards,
Thomas Preud&#
Le jeudi 4 août 2011 00:53:59, grischka a écrit :
> Thomas Preud'homme wrote:
> > Actually I'd like to be able to try 2 prefixs, to reduce the dependencies
> > between glibc and tcc. This way tcc could work well both with the old
> > glibc (which install crt objec
Le samedi 6 août 2011 16:55:15, grischka a écrit :
> Thomas Preud'homme wrote:
> >> Does gcc try prefixes for crt objects?
> >
> > I don't know for the upstream gcc but I did a try on my debian system
> >
> > and it is:
> > [...]
>
>
Le dimanche 7 août 2011 21:38:44, grischka a écrit :
> Thomas Preud'homme wrote:
> >> Anyway I pushed some patches so you can have crtprefix1:crtprefix2.
> >> Note that it's also sysrooted. I don't know why you changed that.
> >
> > Did I? When
e time of pickyness, as I was trying
all the solution to do it without knowing which one you'd prefer. Does
bikeschedshrink exist?
Best regards,
Thomas Preud'homme
signature.asc
Description: This is a digitally signed message part.
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
ame function altogether.
I've just noticed the function should be a bit more constraint to reject files
like AS_NEEDED(AS_NEEDED(…)). Also libname_to_filename should always return .a
for non PE systems, still according to [1]. But don't bother to do t
Greatings everyone,
I've been reading arm-gen.c lately and was a bit surprised by some code
related to struct and float (including double and long double) parameter
passing in gfunc_call. It's probably just a mistake from my reading in which
case I'd appreciate you explained me the bits I misse
Le vendredi 28 octobre 2011 01:19:50, Daniel Glöckner a écrit :
> Hi,
>
> On Fri, Oct 28, 2011 at 12:08:55AM +0200, Thomas Preud'homme wrote:
> > I've been reading arm-gen.c lately and was a bit surprised by some code
> > related to struct and float (including do
Le mercredi 2 novembre 2011 17:29:13, Robert Clausecker a écrit :
> Am Mittwoch, den 02.11.2011, 12:00 -0400 schrieb Ben Bacarisse
>
> > > It seems that I discovered a bug in tcc. ANSI C allows declaration
> >
> > of
> >
> > > prototypes containing function pointers like this:
> > > void
t;);
tcc_define_symbol(s, "__PTRDIFF_TYPE__", "long long");
#else
tcc_define_symbol(s, "__SIZE_TYPE__", "unsigned long");
tcc_define_symbol(s, "__PTRDIFF_TYPE__", "long");
#endif
Best regards,
Le lundi 19 septembre 2011 19:30:09, Thomas Preud'homme a écrit :
> Le lundi 19 septembre 2011 18:49:32, u-tcc-u...@aetey.se a écrit :
> > Hello,
> >
> > I had to apply the following patch to be able to use my uclibc instance
> > which contains relative library
Hi Grischka,
would it be possible to do a new fastforward of the master branch to the
current mob branch ?
Best regards,
Thomas Preud'homme
signature.asc
Description: This is a digitally signed message part.
___
Tinycc-devel mailing list
T
ver returns).
>
> Anyone wants to fix that?
3ab269c56ac1bb79956c0160382bb720ca487ca3
Review welcome, including about the wording.
Best regards,
>
> --- grischka
Thomas Preud'homme
>
> > #include
> > #include
> >
> > int main(void) {
> >
&
gt;49: 8b 5d fcmov0xfffc(%ebp),%ebx
>4c: dd 03 fldl (%ebx)
>
> It should never use %ebx. Hope this helps.
Are you working on a fix? I looked for some use of ebx in i386-* and didn't see
any reference to ebx o
Le lundi 23 janvier 2012 01:53:21, Daniel Glöckner a écrit :
> On Mon, Jan 23, 2012 at 12:14:58AM +0100, grischka wrote:
> > Thomas Preud'homme wrote:
> > >>Similar bug happens for i386 for example with
> > >>
> > >> double bar(double a, do
Le mardi 24 janvier 2012 01:11:08, Daniel Glöckner a écrit :
> On Mon, Jan 23, 2012 at 11:30:54AM +0100, Thomas Preud'homme wrote:
> > Shouldn't the same fix (Cf attached file) be applied for x86-64?
>
> Yes you are right, x86-64 needs fixing as well.
>
> >
Le mardi 24 janvier 2012 13:10:23, grischka a écrit :
> Thomas Preud'homme wrote:
> > Le mardi 24 janvier 2012 01:11:08, Daniel Glöckner a écrit :
> >> On Mon, Jan 23, 2012 at 11:30:54AM +0100, Thomas Preud'homme wrote:
> >>> Shouldn't the same
Le mardi 24 janvier 2012 15:36:27, Thomas Preud'homme a écrit :
> Le mardi 24 janvier 2012 13:10:23, grischka a écrit :
[SNIP]
> > Interpreted version: Before you even start to write some patch, make
> > sure you have a test to prove its correctness.
>
> Don't
to do it you can try the version in experimental in
Debian. For this, just add the following line:
deb ftp://ftp.us.debian.org/debian/ experimental main
to your sources.list, run apt-get update and install tcc again. This package
contains almost all the change fro
Le lundi 5 mars 2012 20:34:51, grischka a écrit :
> Thomas Preud'homme wrote:
> > I would be very grateful if anyone with more knowledge than me could do
> > it.
>
> Anyway before we forget I pushed something.
>
> http://repo.or.cz/w/tinycc.git/commitdiff/
of warning:
tccpp.c:924:22: warning: array index of '2' indexes past the end of an array
(that contains 2 elements) [-Warray-bounds]
str[len++] = cv->tab[2];
I didn't look more into it as I lack of time these days.
Best regards,
Thomas Preud'homme
dpkg-buildpack
I didn't pay attention it was an union. I looked at it quickly but
considerid it as a struct. My bad, I used this structure before and noticed it
is an union at the time.
There is also a warning about a %Lu in tccpp.c but this does not explain the
segfault. I should try running a debugger
ld have had to set correctly "References:" and "In-Reply-To:"
header in the mail to the Message-Id of the mail you want to reply to. But
that's not a big deal, tinycc-devel is not a high volume mailing list.
Best regards,
Thomas Preud'homme
signatur
loading of LLOCAL
floats.
So if anyone want to jump into it, feel free :)
[debian-patch] http://patch-
tracker.debian.org/package/tcc/0.9.26~git20120104.83d57c0-4
Best regards,
Thomas Preud'homme
signature.asc
Description: This is a digitally sign
Le mardi 13 mars 2012 17:02:24, Vincent Lefevre a écrit :
> On 2012-03-13 16:49:37 +0100, Vincent Lefevre wrote:
> > FYI, the problem occurs for shift counts from 32 to 63 (larger
> > shift counts are invalid in C, since the variable is on 64 bits).
>
> The bug disappears when I replace 1UL by: (u
Greetings everybody,
when reading tccgen.c vnrott and vrotb came to be on the same screen and I
wondered what is the reason to have both of them. They do the same thing, so i
was wondering about removing one in favor of the other. If one had to be
removed, I would favor vnrott as it has the sa
Le mercredi 14 mars 2012 00:36:06, Daniel Glöckner a écrit :
> On Tue, Mar 13, 2012 at 05:56:12PM +0100, Thomas Preud'homme wrote:
> > when reading tccgen.c vnrott and vrotb came to be on the same screen and
> > I wondered what is the reason to have both of them. They do the
ker option '-rpathstuff'" instead of "unsupported linker option
'-rpathstuff,--oformat,coff'.
Best regards,
Thomas Preud'homme
signature.asc
Description: This is a digitally signed message part.
___
Tinycc-dev
Le jeudi 15 mars 2012 22:53:14, grischka a écrit :
> Thomas Preud'homme wrote:
> > In other words, tcc -o foo -Wl,-rpathstuff,--oformat,coff will correctly
> > says "unsupported linker option '-rpathstuff'" instead of "unsupported
> > linker opti
Le vendredi 16 mars 2012 00:39:37, grischka a écrit :
> Thomas Preud'homme wrote:
> > Can you give me an example which fails for you?
>
> $ tcc libtcc.c -DONE_SOURCE -shared -o libtcc.so -ldl
I had to add -DTCC_IS_NATIVE
> $ tcc tests/libtcc_test.c -I. -o libtcc_test libt
Le vendredi 16 mars 2012 22:31:18, grischka a écrit :
> Thomas Preud'homme wrote:
> >> $ tcc libtcc.c -DONE_SOURCE -shared -o libtcc.so -ldl
> >
> > I had to add -DTCC_IS_NATIVE
>
> Because you missed -DTCC_TARGET_X86_64 ;)
The configure did. Even if I add it
Le mardi 20 mars 2012 10:42:25, grischka a écrit :
> Thomas Preud'homme wrote:
> > What do you think of this patch? I tried with my example and yours but
> > I'm afraid of breaking things now so I prefer to attach it here.
>
> The problem with examples is that the
Le mardi 20 mars 2012 12:44:25, grischka a écrit :
> Thomas Preud'homme wrote:
> >> The problem with examples is that they can show bugs that exist, but
> >> not really the absence of bugs. To test such feature I'd rather use
> >> some printf here or there.
Le mardi 20 mars 2012 10:42:25, grischka a écrit :
> Thomas Preud'homme wrote:
> > What do you think of this patch? I tried with my example and yours but
> > I'm afraid of breaking things now so I prefer to attach it here.
>
> The problem with examples is that the
th correspond to what -I does. So I would say it's the
normal behaviour.
>
> That, of course, is a Perl script. I will be happy to boil this down to a C
> program, but I first wanted to be sure that I hadn't lost my mind.
>
> Thanks!
e the
delay
Best regard,
Thomas Preud'homme
--- Begin Message ---
Use CString to concat linker options
Can you help me to find the missing library references, or fix the build?
I liked everything that you were doing,
until...
you added the use of CString.
I am using TDM32 version of GCC an
Le lundi 9 avril 2012 23:48:45, Daniel Glöckner a écrit :
> On Mon, Apr 09, 2012 at 05:39:48PM +0200, Thomas Preud'homme wrote:
> > A few days ago[0] I received an email from someone who can't compile tcc
> > since I introduce the use of CString to concat linker opti
Le lundi 9 avril 2012 23:52:42, Thomas Preud'homme a écrit :
> Le lundi 9 avril 2012 23:48:45, Daniel Glöckner a écrit :
> > On Mon, Apr 09, 2012 at 05:39:48PM +0200, Thomas Preud'homme wrote:
> > > A few days ago[0] I received an email from someone who can't co
ndows well
enough to be sure of what I am doing. So if someone *know* it's fine to build
both with ONE_SOURCE then please change it.
>
> I also have a simple change request; can someone add this simple patch
> to add "nostdlib" to libtcc?
> Or is there anything against it?
, can there be? :)
The last release is indeed the 0.9.25. There will be a release soon, but the
soon is not defined yet.
Best regards,
Thomas Preud'homme
signature.asc
Description: This is a digitally signed message part.
___
Tinycc-dev
nul byte was systematically added or maybe I just
forgot. Thanks.
I saw a cstr_new at the top, did I forget it when reverting? Damn me.
About the cstr_*, are they now part of the library on Windows? I mean if they
are exported some people might
-run" which is then
obviously not found. Should we go back to the solution proposed in [2] or do
you have another idea?
[2] cb2138f8b098feb1b51a407343a4b99e25d5b506
Best regards,
Thomas Preud'homme
signature.asc
Description: This is a digi
Le jeudi 10 mai 2012 15:50:00, Thomas Preud'homme a écrit :
> Greetings everybody,
>
> I've just realized that the env trick to use tcc from the correct place [1]
> doesn't work because neither Linux nor env split arguments at spaces.
>
> [1] See commit 27a428c
aligned
in the diff.
Anyway, I'm very eager to have feedback of any kind. If there is a blatant bug
I'd like to hear about it.
Best regards,
Thomas Preud'homme
diff --git a/arm-gen.c b/arm-gen.c
index b7e8665..b535712 100644
--- a/arm-gen.c
+++ b/arm-gen.c
@@ -737,16 +
like to get?
>
> It would be nice if there was some way this could be included in future
> versions,
>
> /PA
Best regards,
Thomas Preud'homme
signature.asc
Description: This is a digitally signed message part.
___
Tinyc
Best regards,
Thomas Preud'homme
signature.asc
Description: This is a digitally signed message part.
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Le vendredi 25 mai 2012 20:48:44, Thomas Preud'homme a écrit :
> Greetings everyone,
>
> it seems the define for pthread_cleanup_push in glibc uses __builtin_expect
> if it's not compiled with gcc. Hence, any program including pthread.h
> fails to compile w
in /usr/local then there's even nothing to do as it's the default.
> > What do you get when running ./configure and what would you like to get?
> >
> > > It would be nice if there was some way this could be included in future
> > > versions,
> > >
&
Le lundi 28 mai 2012 20:50:27, grischka a écrit :
> Thomas Preud'homme wrote:
> > Grishka, would the following patch be fine with you? I saw you add the
> > change to error out on unknown option.
>
> Sure. I've added that because I want some feedback when I misty
Le vendredi 25 mai 2012 22:57:54, Thomas Preud'homme a écrit :
> Le vendredi 25 mai 2012 20:48:44, Thomas Preud'homme a écrit :
> > Greetings everyone,
> >
> > it seems the define for pthread_cleanup_push in glibc uses
> > __builtin_expect if it's
Debian. I'm not
involved enough to pretend influencing the direction tcc should take.
Anyway, thanks for all the patch which will flow in tcc. It's good to see
activity here and on mob.
Best regards,
Thomas Preud'homme
signatur
Le mardi 29 mai 2012 21:03:18, grischka a écrit :
> Thomas Preud'homme wrote:
> >>> it seems the define for pthread_cleanup_push in glibc uses
> >>> __builtin_expect if it's not compiled with gcc. Hence, any program
> >>> including pthr
(possibly until end of august) so feel free to
investigate if you care about this bug. I checked against the mob branch and
this bug do apply so it is not a bug coming from Debian.
[1] http://bugs.debian.org/675024
Best regards,
Thomas Preud'homme
signature.asc
Description: This is a d
e.org/bugzilla/show_bug.cgi?id=14188
>
> Miki.
Best regards,
Thomas Preud'homme
signature.asc
Description: This is a digitally signed message part.
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Le jeudi 31 mai 2012 22:49:19, grischka a écrit :
> Thomas Preud'homme wrote:
> > Le jeudi 31 mai 2012 22:31:55, Milutin Jovanović a écrit :
> > > How about asking them (glibc people)? Maybe they have a reason for
> > > this.
> > >
> > > May
Le lundi 4 juin 2012 21:51:27, Daniel Glöckner a écrit :
> Hi Thomas,
>
> On Tue, May 22, 2012 at 03:42:47PM +0200, Thomas Preud'homme wrote:
> > I added support for arm hardfloat calling convention (standard variant in
> > AAPCS) and I would appreciate some feedback
Le mercredi 6 juin 2012 00:35:09, Daniel Glöckner a écrit :
> On Mon, Jun 04, 2012 at 10:49:35PM +0200, Thomas Preud'homme wrote:
> > I might be able to give you an access to a Debian porterbox. Would you be
> > interested?
>
> Thanks, but no.
> These days I don
Greetings grischka,
sorry to bother you again but would you mind bumping master to the current mob
in the next days? By the way, when do you plan to do a release of tcc?
Best regards,
Thomas Preud'homme
signature.asc
Description: This is a digitally signed message
Le dimanche 10 juin 2012 12:09:37, Daniel Glöckner a écrit :
> On Sun, Jun 10, 2012 at 09:15:52AM +0200, Michael Matz wrote:
> > Thomas: as you were last fiddling with arm, you might want to check
> > if the test works on it. The other alloca testcase is #ifdef'ed on
> > i386 and x86_64, but that
doesn't use VFP so it will work for both ABI. It also work for the new
eabihf which I introduced as there is no float parameter.
>
>
> Ciao,
> Michael.
Best regards,
Thomas Preud'homme
signature.asc
Description: This is a digitally signed message part.
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Le mardi 12 juin 2012 15:56:57, vous avez écrit :
> Thomas Preud'homme wrote:
> > Greetings grischka,
> >
> > sorry to bother you again but would you mind bumping master to the
> > current mob in the next days? By the way, when do you plan to do a
> >
Le mardi 12 juin 2012 17:24:20, Thomas Preud'homme a écrit :
[SNIP]
>
> I've just created an account robotux on repo.or.cz.
Sorry, the login is case sensitive. It's RoboTux then.
Thanks for the bump by the way.
>
> Best regards,
>
> Thomas Preud'hom
rading my i386 VM to test
it for completeness.
>
> Miki.
Regards,
Thomas Preud'homme
signature.asc
Description: This is a digitally signed message part.
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mai
ple the package is not uploaded if the testsuite
fails.
Best regards,
Thomas Preud'homme
signature.asc
Description: This is a digitally signed message part.
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Le vendredi 6 juillet 2012 14:25:54, Vincent Lefevre a écrit :
> On 2012-07-06 13:33:23 +0200, Vincent Lefevre wrote:
> > I've rewritten my tests to be added to the test suite and improved
> > them. They show that my patch was actually incorrect when the
> > first argument is unsigned short: the ty
No plan yet but when I'll be done with armhf support I might be tempted. This
means at least not before several months though. Do you have a link to the
ABI, especially calling convention since syscall will be handled by the libc?
Best regards,
Thomas Preud'homme
signature.asc
Descrip
think speed is not a major concern when compiling with tcc (there is gcc or
llvm for this) hence this should be fine.
However this is just words for the moment, as I said I will not be able to
work on it before at least several month (3 but probably more).
Best regards,
Thomas Preud&#
Le mardi 12 juin 2012 17:24:20, Thomas Preud'homme a écrit :
[SNIP]
>
> Oh dear, it misses a break indeed. I don't remember the exact test I did
> but that was a home made assembly file with no code so I couldn't test the
> output. I did however checked the res
e
end of the function, just before the #ifdef TCC_TARGET_C67 vtop->r is set
again to r whereas the value is no longer in r.
Attached is a patch. It's not the best solution, but that's the first I found.
Improvement welcome.
Despite this, the following testcase still fails:
#includ
Le mercredi 11 juillet 2012 19:45:23, Thomas Preud'homme a écrit :
> Le samedi 9 juin 2012 15:57:03, g...@sdf.org a écrit :
> > Hi list,
> >
> > Here is a simple C program that does not compile and execute correclty
> > with TCC (on i386, both with TCC 0.9.25
o you know any place in the code which could rely on the
previous behavior of get_reg()? If yes please revert the commit
d1694f7d7e6d96f64d1330c9b43491b613272b1e.
Best regards,
Thomas Preud'homme
diff --git a/tccgen.c b/tccgen.c
index d27bdba..e27590c 100644
--- a/tccgen.c
+++ b/tccgen.c
> Attached is an email patch.
>
> -spc (For the curious, I made a Lua module for TCC, and it's Lua that
> manages the memory for my application)
Best regards,
Thomas Preud'homme
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
(the architecture for which tcc
generates code). For instance, although tcc doesn't support MIPS, it can run
on MIPS and create program for x86, x86-64 and arm.
Best regards,
Thomas Preud'homme
signature.asc
Description: This is a digitally signed message part.
ure
linux support except I recall a comment about endianness issue so that may be
not completely true. Anyway in your case if you want tcc to be useful (that is
runs the code it generates) you need it to support the platform it runs on.
Best regards,
Thomas Preud'homme
g a different compiler, if I
> find it.
If you target code efficiency (wether in speed or size), you can take a look
into gcc or llvm.
>
> > David
Regards,
Thomas Preud'homme
signature.asc
Description: This is a digitally signed message part.
101 - 200 of 620 matches
Mail list logo
