Le jeudi 17 janvier 2013 01:48:01, Michael Matz a écrit :
Hi,
Pointer to integer conversions (and back) are implementation defined, the
only requirement being that if the integer type is (u)intptr_t that a
pointer converted to that one and back to a pointer shall compare equal to
the
I guess but as I said I
don't know anything about this flag (first time I hear about it).
Best regards,
Thomas Preud'homme
---BeginMessage---
Package: tcc
Version: 0.9.26~git20120612.ad5f375-6
Severity: normal
TCC doesn't set the FE_INVALID flag on comparison with NAN (=, =, , ),
at least
is consistent to gcc. I'm not sure what the correct value (if
any) should be though.
Best regards,
Thomas Preud'homme
signature.asc
Description: This is a digitally signed message part.
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https
at the best time :)
[1] http://lists.nongnu.org/archive/html/tinycc-devel/2013-01/msg5.html
Best regards,
Thomas Preud'homme
signature.asc
Description: This is a digitally signed message part.
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https
Le dimanche 6 janvier 2013 17:03:28, grischka a écrit :
Other candidates for reversion (OTOH):
-
http://repo.or.cz/w/tinycc.git/commitdiff/fc574f14984d11f1ead50560d1bdc5ae
0eaf6d8d The headers from include are copied to win32/include during
install
I'm not sure to understand why
Hi Akim,
Le dimanche 13 janvier 2013 23:30:49, Thomas Preud'homme a écrit :
In the case we had some warnings I'd still prefer to not use
-D_FORTIFY_SOURCE 0. The first reason is that _FORTIFY_SOURCE does 2
things: it hardens the source by adding some buffer overflow checks and it
adds more
Le lundi 14 janvier 2013 18:01:08, Akim Demaille a écrit :
Le 14 janv. 2013 à 17:55, Thomas Preud'homme robo...@celest.fr a écrit :
Hi Akim,
Hi Thomas,
If there were other messages for me, I might have missed them :(
Can you explain me what is the purpose of second part of the sed
Le lundi 14 janvier 2013 18:47:12, Akim Demaille a écrit :
Le 14 janv. 2013 à 18:23, Thomas Preud'homme robo...@celest.fr a écrit :
What do you think of the proposed fix? It works for me at least. It first
look at the directory in which the symlink is to be done and strip
entirely the path
Le dimanche 6 janvier 2013 17:03:28, grischka a écrit :
/usr/bin/gcc-4.0.4 -o tcc.o -c tcc.c -DTCC_TARGET_I386 -I.
-I/home/didier/documents/tech/dev/tcc/tinycc -Wall -g -O2
I think some people might not feel comfortable to see their absolute
paths exposed. Also it makes command lines
Le dimanche 6 janvier 2013 09:36:05, Aharon Robbins a écrit :
Hi Thomas.
TCC on the mob branch has progressed quite a lot. I use it for testing
compilation of gawk (GNU Awk). It is quite fast, which is a significant
pleasure compared to gcc or clang. The released version did compile
gawk
Le dimanche 6 janvier 2013 11:28:39, Didier Barvaux a écrit :
Thomas,
Hi Olivier,
I performed some tests on a Linux x86 system with the various compilers
available on that system.
For all tests, GIT revision was
fc574f14984d11f1ead50560d1bdc5ae0eaf6d8d
thanks for all these tests, it's
Le dimanche 6 janvier 2013 17:25:59, grischka a écrit :
grischka wrote:
-
http://repo.or.cz/w/tinycc.git/commitdiff/3d409b08893873b917ccb8c34398bc
41a4e84d7c
The patch doesn't fix the real problem which is not duplicate -I's by
the user but the very obviously crappy handling of
Le mercredi 5 décembre 2012 10:24:51, Somchai Smythe a écrit :
Hello,
From the snapshot of tcc mob I downloaded today, I see this when I
compile:
clang -o x86_64-gen.o -c x86_64-gen.c -DTCC_TARGET_X86_64 -O3 -m64
-march=x86-64 -mtune=generic -pipe -fno-strict-aliasing
Le jeudi 13 décembre 2012 17:55:41, vous avez écrit :
[SNIP]
from arch/arm/kernel/stacktrace.c:
* With framepointer enabled, a simple function prologue looks like
this: * mov ip, sp
* stmdb sp!, {fp, ip, lr, pc}
* sub fp, ip, #4
*
* A simple
What would you think of this simpler patch instead? It works on you fp.c code
at least and it should work for any level.
It's a simple proof of concept as of now because I'm not sure how the
addresses of local variables are stored in tcc. Thus, I'm not sure that this
doesn't break access to
Le samedi 5 janvier 2013 16:35:44, vous avez écrit :
Are you sure the code you compiled for ARM doesn't contain
__builtin_return_address instead of __builtin_frame_address?
Thomas, thanks for correcting my arm assembly errors. I agree I did make
mistakes, but I'm sure
Greetings dear fellow tinycc developers and enthousiasts,
In preparation of the upcoming release of tinycc 0.9.26, I would like to have
reports about how tcc build and works to be sure it is as stable as possible.I
tried quickly on my arm machine and will continue to do experiment on that
Le mardi 18 décembre 2012 21:29:22, grischka a écrit :
I can provide help to provide other useful targets, such
as make dist and make distcheck.
Thomas who manages a distro (debian) might want to comment.
Sorry, I never used these targets yet in the projects I touched. What are they
Le mercredi 19 décembre 2012 15:20:41, grischka a écrit :
I see. Our tarballs here were made from a fresh git checkout except
that tcc-doc.html was added and win32/build-tcc.bat was converted
to CRLF endings:
http://download.savannah.gnu.org/releases/tinycc/
I think git could be
Le dimanche 16 décembre 2012 17:45:43, grischka a écrit :
A release is planned soon so please be careful.
About that I'm sorry, I didn't manage to announce it before I got too busy.
Since it will be christmas soon and many people will stop reading news about
software, my plan is to release
Le jeudi 6 décembre 2012 04:50:55, vous avez écrit :
Hi Kirill,
did you make any progress on the issue since Daniel's comments? Could you
let me know when you push a patch so that I can test it and bump master
to equal the mob branch?
Hi Thomas,
Unfortunately not that much. I
Le jeudi 6 décembre 2012 17:00:40, grischka a écrit :
Well, release would be fine for me. Honestly, even better if someone else
could do it. Steps IIRC are:
- update Changelog and VERSION
- tag the git revision
- pack archives and upload to savannah
many things to improve, including some I care about, but
it might attract new contributions or new users to have a more recent release.
What do you think?
Best regards,
Thomas Preud'homme
signature.asc
Description: This is a digitally signed message part
Le samedi 24 novembre 2012 10:02:54, Kirill Smelkov a écrit :
Thanks for the info. The progress on my side is as follows: I've learned
arm assembly and setup arm and armhf cross-toolchains (turned out to be
very easy, thanks to emdebian[1]). Also I can run arm binaries via
qemu-arm and basic
Greetings Daniel,
while reading code in arm-gen.c recently I stumbled upon what I think is a bug
I introduced with the hard float calling convention. Two places in register
assignment code assume that at the top of the value stack (the place pointed
by vtop) is a LLONG pushed for 8 bytes
On Thu, 22 Nov 2012 13:37:16 +0400, Kirill Smelkov wrote:
I don't like that filter-out's. Actually, what I'd like to write here
is
ifeq ($(CONFIG_TCC_BCHECK),y)
TESTS += btest
endif
I agree it fits more my mental model.
or even better
TESTS-$(CONFIG_TCC_BCHECK) +=
, fix it.
No need to blame yourself, this line is not necessary. Besides, this
information can be extracted from git log/blame.
Reported-by: Thomas Preud'homme robo...@celest.fr
---
tests/Makefile | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/tests/Makefile b/tests
Le jeudi 15 novembre 2012 18:34:51, grischka a écrit :
robo...@celest.fr wrote:
I already did a general function to store a value but I adopted a
different approach:
#define put_sym_attr(s,index,field,val) \
alloc_sym_attr(s, index); \
s-sym_attrs[index].field =
Le vendredi 16 novembre 2012 22:07:52, Thomas Preud'homme a écrit :
Le jeudi 15 novembre 2012 18:34:51, grischka a écrit :
Compare
put_sym_attr(s1, sym_index, got_offset, s1-got-data_offset);
with
alloc_sym_attr(s1, sym_index)-got_offset = s1-got-data_offset
Le dimanche 11 novembre 2012 17:14:45, Milutin Jovanović a écrit :
Hi,
Sorry for resurecting an old thread, but I do believe it is related. I am
having some trouble passing tests on Raspberry Pi (armv6 vfp), specifically
float point ones.
Below pseude code is my understanding of compiler
architecture: 7
CPU variant : 0x0
CPU part: 0xb76
CPU revision: 7
Hardware: BCM2708
Revision: 000f
Serial : 320cbf84
Was I suppose to fix something else based on this?
Best regards,
Thomas Preud'homme
signature.asc
Description
Le dimanche 11 novembre 2012 19:53:27, Christian Jullien a écrit :
[SNIP]
I get
tcc: error: undefined symbol '__aeabi_idiv'
tcc: error: undefined symbol '__aeabi_idivmod'
[SNIP]
Changing int to unsigned int results in:
tcc: error: undefined symbol '__aeabi_uidiv'
tcc:
Le samedi 10 novembre 2012 16:33:33, Daniel Glöckner a écrit :
On Wed, Nov 07, 2012 at 04:18:00PM +0100, Thomas Preud'homme wrote:
Le mercredi 7 novembre 2012 16:09:51, Milutin Jovanović a écrit :
Other then that, looks OK to me. BTW, I did not check correctness, just
reviewed the style
Le samedi 10 novembre 2012 17:14:48, Thomas Preud'homme a écrit :
Le samedi 10 novembre 2012 16:33:33, Daniel Glöckner a écrit :
Can we assume GOT entries are aligned to 2 bytes on all architectures?
It's the case for i386, amd64 and arm EABI at least. The first patch I
proposed only
Le lundi 5 novembre 2012 14:01:20, Hitoshi Mitake a écrit :
Hi tcc folks.
I found a trivial bug of tcc. Current tcc permits comparison of
structs and comparison between struct and other typed values. This
patch can fix the bug.
I'm new to tcc. Sorry if this patch contains wrong part.
I'd
are in mood. Some users at least
would be happy.
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
is that nocode_wanted should be 1 if processing some static
variable since it will be outside any function. This is probably the easiest
fix but really both problems should be fixed IMHO.
Regards,
Didier
Thanks for the report.
Best regards,
Thomas Preud'homme
signature.asc
Description
Le dimanche 21 octobre 2012 13:48:18, Thomas Preud'homme a écrit :
The second mistake is that nocode_wanted should be 1 if processing some
static variable since it will be outside any function. This is probably
the easiest fix but really both problems should be fixed IMHO.
Since VLA
Le dimanche 21 octobre 2012 13:51:16, Thomas Preud'homme a écrit :
Le dimanche 21 octobre 2012 13:48:18, Thomas Preud'homme a écrit :
The second mistake is that nocode_wanted should be 1 if processing some
static variable since it will be outside any function. This is probably
the easiest
Le jeudi 18 octobre 2012 19:40:50, grischka a écrit :
Thomas Preud'homme wrote:
#13213 cannot use integer for array size
#14957 `-b' simply doesn't work when supplied with `-run' in `#!'-lines
#15332 static var initialization
#23851 no DESTDIR support
I've close these as Fixed
doesn't work when supplied with `-run' in `#!'-lines
#15332 static var initialization
#23851 no DESTDIR support
I'll try to take a closer look at the other when I'll find motivation.
Best regards,
Thomas Preud'homme
signature.asc
Description: This is a digitally signed message part
Le mercredi 17 octobre 2012 23:17:23, arn...@skeeve.com a écrit :
Hi. Occasionally I use tcc on x86_64 for testing building gawk with
something that isn't GCC. I'm getting this:
../gawk: Symbol `malloc' causes overflow in R_X86_64_PC32 relocation
../gawk: Symbol `free' causes overflow in
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
signature.asc
Description: This is a digitally signed message part
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
]);
printf (%lld %lld\n, ll[lli], ll[lli]);
printf (%lld\n, ll[lli]);
return 0;
}
I probably won't have time to look into it before quite some time so help
welcome to find the bug.
Best regards,
Thomas Preud'homme
___
Tinycc-devel mailing list
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 and with the latest sources; it
works
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
@@ -589,11
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 result of the relocation and I remember
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
Description: This is a digitally
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'homme
signature.asc
Description
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 type
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
release of tcc?
Best regards,
Thomas
for the assembler implementation (don't know if it would have to
differ between the eabi and oldabi variants).
It 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
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 part
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 on the patch.
there I
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 digitally signed
/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 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 not compiled with gcc. Hence, any program
including
way this could be included in future
versions,
/PA
Best regards,
Thomas Preud'homme
Salut Thomas,
I fear I didn't tell the whole story , sorry :( The problem is not when you
call ./configure directly but when you call it from dpkg-buildpackage to
actually build
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 mistype stuff.
Maybe just to be similar
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.
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org
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 with tcc. Should we ignore __builtin_expect
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 digitally signed message part
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 27a428cd0fae475d7377e1dbe218c064ee217d85
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-devel mailing list
Tinycc-devel@nongnu.org
, 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 start to use them, no?
--- grischka
Best regards,
Thomas Preud'homme
___
Tinycc-devel
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?
Regards,
Gabriel
Best regards,
Thomas Preud'homme
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 compile
tcc since I introduce the use
the
delay
Best regard,
Thomas Preud'homme
---BeginMessage---
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 and building TCC
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 options.
Unfortunetely, I cannot
.
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!
David
Thomas Preud'homme
signature.asc
Description: This is a digitally signed message part.
___
Tinycc
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 they can show bugs that exist
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.
And valgrind to test you don't free too
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 they can show bugs that exist
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 libtcc.so -ldl
-Wl,-rpath=`pwd
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 option '-rpathstuff,--oformat,coff'.
Well, but did you test
'-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-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org
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
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 same
thing, so i
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-buildpackage: source package tcc
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
signature.asc
Description: This is a digitally signed message part
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/ae191c3a619db25e3c9d4b6c89d1a997
0563d825
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 from the mob branch.
Thanks,
Arnold
Best regards,
Thomas Preud'homme
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 worry, that's what I do before committing
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.
As I'm not sure about the answer I didn't dare
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 fix (Cf attached file) be applied for x86-64?
Yes you
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, double b, double c, double d);
double foo (double *p
the wording.
Best regards,
--- grischka
Thomas Preud'homme
#include windows.h
#include stdio.h
int main(void) {
int retCode = 0;
PROCESS_INFORMATION pi;/* filled in by CreateProcess */
STARTUPINFO si;/* startup info for the new process
of ebx in i386-* and didn't see
any reference to ebx or rbx which looked suspicious. Would it be a wrong
construction of an instruction?
--- grischka
Best regards,
Thomas Preud'homme
Regards
Andreas Eriksson
___
Tinycc-devel mailing list
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
Tinycc
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
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
(str, c);
}
I guess you did it this way to avoid just forbidding {b} but allowing any {x}
with x ≠ b. Anyway, you saved me from more 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
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? I was probably not careful enough.
No, it seems you wanted
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 objects in /usr/lib) and the current glibc
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:
[...]
Sure, why else should they have 250kb of gcc.c driver code.
Attached
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'homme
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 (which is fine in Debian since only native tcc
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 elf
interpreter (it's part of the ABI
301 - 400 of 466 matches
Mail list logo
