Le vendredi 23 août 2013 14:54:57 David Mertens a écrit :
Hello everyone -
Useful build reports are coming in. Apparently the recipe is the main
culprit at the moment, but I wanted to draw attention to a few things.
BSD needs gmake for tcc's makefile
OpenBSD --
Le mercredi 21 août 2013 08:41:09 David Mertens a écrit :
Hey everyone -
Another important aspect of interest for the tinycc community is that a
number of people or companies run and report automated smoke systems on all
Perl modules that get uploaded to CPAN. This means I will get
Le vendredi 16 août 2013 20:38:06 Anton Shepelev a écrit :
Hello all,
Hi Anton,
sorry for the late answer.
The manual says:
The default system include paths are: '/usr/
local/include', '/usr/include' and 'PREFIX/lib/
tcc/include'. ('PREFIX' is usually '/usr' or
Le lundi 8 juillet 2013 23:07:28, Ben a écrit :
Q: is top-posting the norm here? I've bottom-posted my reply but that
might just be making things worse if top-posting is usual.
AFAIK the norm on mailing list is bottom-posted. I've always bottom-posted
here but some people top-post so you
Le vendredi 14 juin 2013 00:34:32, Thomas Preud'homme a écrit :
Got it, thanks. I've just tested that and the problem is that the load is
not defined for bool type on amd64 architecture. Should be easy to fix but
now is time to sleep.
I'll push a fix tomorrow.
Should be fixed now. I also
Le dimanche 26 mai 2013 10:40:38, Aharon Robbins a écrit :
Hi. I just pulled mob and rebuilt and installed. Now trying to build gawk
I get:
tcc -DDEFPATH='.:/usr/local/share/awk'
-DDEFLIBPATH=\/usr/local/lib/gawk\ -DSHLIBEXT=\so\ -DHAVE_CONFIG_H
-DGAWK
Le jeudi 13 juin 2013 20:22:21, Aharon Robbins a écrit :
Hi Thomas.
You need current gawk. Either http://ftp.gnu.org/gnu/gawk/gawk-4.1.0.tar.gz
or
git clone git://git.savannah.gnu.org/gawk.git
cd gawk
./bootstrap.sh
./configure CC=tcc
make make check
Le mardi 11 juin 2013 21:12:15, Stephan Beal a écrit :
On Tue, Jun 11, 2013 at 8:41 PM, Stevie G. Messervey
nuke48...@yahoo.comwrote:
#!/usr/local/bin/tcc -run -Iinclude -Llib -lccgi -luuid -lgmp -lcrypt
-lsqlite3 -lmagic -lgd -lcurl -lquickmail -lgif -lfoo -lbar
Take note the space
Le jeudi 6 juin 2013 06:37:39, Christian Jullien a écrit :
Hi all,
Is someone working on this issue?
Raspberry Pi is still broken (tested with last night commit)
ret_double_test... success
ret_longdouble_test... success
ret_2float_test... Segmentation fault
Sorry no. I haven't had any
Le mercredi 22 mai 2013 15:25:26, Armin Steinhoff a écrit :
Hi All,
I have ported tcc to the BeagleBone running QNX 6.5.
Starting tcc-arm w/o parameters shows the expected help informations.
The command tcc-arm -c ex5.c works ... it creates ex5.o
Linking the executable with tcc-arm
Le samedi 4 mai 2013 15:12:20, Stephan Beal a écrit :
Hiho,
i just updated to the latest tcc:
[stephan@host:~/cvs/tinycc]$ git pull
...
From git://repo.or.cz/tinycc
...
And i am seeing what is probably a portability problem on x64 Ubuntu 12.04:
[stephan@host:~/cvs/fossil/cpdo]$
Le jeudi 2 mai 2013 13:28:52, Daniel Glöckner a écrit :
Hi Rune,
On Thu, May 02, 2013 at 10:37:58AM +, u-tcc-u...@aetey.se wrote:
From my perspective I'd like to skip the additional worry about which
programs can be linked to which libraries and how.
if you are a packager, why do
Le mercredi 1 mai 2013 05:54:54, KHMan a écrit :
On 5/1/2013 9:51 AM, Rob Landley wrote:
On 04/30/2013 11:53:31 AM, Daniel Glöckner wrote:
On Tue, Apr 30, 2013 at 05:43:03PM +0200, Thomas Preud'homme wrote:
As I already said privately, I'm fine with BSD-2-clause.
Does that mean you
Le mercredi 1 mai 2013 16:59:25, Daniel Glöckner a écrit :
Hi Thomas,
I saw that you used the following line to store the floating point
arguments that have been passed in fpu register:
o(0xED2D0A00|nf); /* save s0-s15 on stack if needed */
In my 2nd edition ARM ARM this maps to the
Le mardi 30 avril 2013 15:40:43, grischka a écrit :
... and since I got permission from Fabrice to use his
original tcc code under a BSD license ...
Actually it's a long standing offer from Fabrice, also repeated
lately on the occasion of the 0.9.26 release.
Yes, sorry. I weant to send an
Le mardi 30 avril 2013 18:53:31, Daniel Glöckner a écrit :
On Tue, Apr 30, 2013 at 05:43:03PM +0200, Thomas Preud'homme wrote:
As I already said privately, I'm fine with BSD-2-clause.
Does that mean you prefer it over the LGPL?
What about you, grischka? Which one do you prefer?
Mmmmh
Le vendredi 26 avril 2013 21:27:25, James Lyon a écrit :
Hi,
I don't have an ARM test system available but it is a new test...
The idea of abitest is to check compatibility of TCC calling convention
with GCC, but I also made rather a lot of changes since compatibility
with GCC on x86 an
Le jeudi 25 avril 2013 14:31:12, ggasnie...@free.fr a écrit :
So, better support for ARM architectures could be great.
I'm currently implementing the Runtime ABI for ARM in the libtcc but I can't
manage to motivate me these days so my progress is very (very) slow. I'll keep
you informed.
Le vendredi 5 avril 2013 09:54:20, Aharon Robbins a écrit :
Hi.
So, I'll be a pest again, and ask - now that we're after the release,
any chance that relocation issues with ELF shared libraries will be fixed
soon? This one issue prevents me from using tcc as my regular compiler
for gawk
Le lundi 25 mars 2013 15:59:21, Jov a écrit :
the README doc is much out fo date,I make a patch to fix these:
1.add x86_64/arm arc support
2.add FreeBSD/OSX support
3.fix make to gmake,because tcc use the gnu make tool,this is different
from make in Freebsd
4.add Texi2html is denpended for
Le mercredi 20 mars 2013 04:10:28, Austin English a écrit :
Howdy,
I'm trying to narrow down a file that fails to compile with tinycc,
but works with gcc/clang. The exact error is:
stateblock.c:875: error: '}' expected (got ,)
Note that you should precompile with tcc itself if you want to
Le mardi 19 mars 2013 06:39:40, Christian Jullien a écrit :
Hi guys,
I've no time to investigate but yesterday commit breaks tcc (at least on
RPi)
I made a clean install and still got:
tccrun.c: In function 'set_pages_executable':
tccrun.c:228:24: error: 'prog_main' undeclared (first
Can you check this new patch works when using libgcc configuration?
Best regards,
Thomas
diff --git a/lib/libtcc1.c b/lib/libtcc1.c
index dacee28..bfe683b 100644
--- a/lib/libtcc1.c
+++ b/lib/libtcc1.c
@@ -689,3 +689,14 @@ void __va_end(struct __va_list_struct *ap)
}
#endif /* __x86_64__ */
Hi there,
when packaging TinyCC 0.9.26 for Debian I noticed a build failure on arm with
EABI calling convention. A bit puzzled at the failure after all the testing
done (this bug didn't show up on my hardware), I then started to investigate.
After some look at the code, I asked for help to
Le dimanche 17 février 2013 21:00:56, Christian Jullien a écrit :
_ _STDC_HOSTED_ _ The integer constant 1 if the implementation is a hosted
implementation or the integer constant 0 if it is not.
What NULL means? Is __STD__HOSTED__ is defined or not? With which value?
To me:
_
Hi Milutin,
in tests/tests2/LICENSE, you wrote:
The tests in this directory are either directly copied from the picoc project
or are subsequently modified and added to for the purpose of TinyCC project.
All these modifications are licensed under the same terms as TinyCC as
specified in the
library not under tcc control)
So what do you think of the attached patch?
Best regards,
Thomas
From fe64a4d00512740b3cd3a8faa49ba7c908e86944 Mon Sep 17 00:00:00 2001
From: Thomas Preud'homme robo...@celest.fr
Date: Sun, 17 Feb 2013 19:44:55 +0100
Subject: [PATCH] Define __STDC_HOSTED__
Le samedi 16 février 2013 10:42:17, Thomas Preud'homme a écrit :
So here are some checksum:
MD5: 5fb28e4abc830c46a7f54c1f637fb25d
SHA1: 7110354d3637d0e05f43a006364c897248aed5d0
SHA256: 521e701ae436c302545c3f973a9c9b7e2694769c71d9be10f70a2460705b6d71
See attached the corresponding gpg
Le samedi 16 février 2013 18:28:52, Christian Jullien a écrit :
c:\tmpgit clone git://repo.or.cz/tinycc.git
Cloning into 'tinycc'...
remote: Counting objects: 5037, done.
remote: Compressing objects: 100% (1558/1558), done.
remote: Total 5037 (delta 3427), reused 5037 (delta 3427)
Receiving
Le samedi 16 février 2013 23:05:54, Austin English a écrit :
On Fri, Feb 15, 2013 at 5:42 PM, Thomas Preud'homme robo...@celest.fr
wrote:
Le vendredi 15 février 2013 19:14:23, Austin English a écrit :
This was around before 0.9.26, but I forgot to report it:
make[1]: Leaving directory
Le vendredi 15 février 2013 07:11:58, Christian Jullien a écrit :
Yesterday, Grischka applied my patch to remove last warning (thanks
Grischka), tcc compiled with NO warning at all.
This morning, with no changes on my config (same compiler, same options,
same script to fetch mod and
Le vendredi 15 février 2013 07:11:58, Christian Jullien a écrit :
Yesterday, Grischka applied my patch to remove last warning (thanks
Grischka), tcc compiled with NO warning at all.
This morning, with no changes on my config (same compiler, same options,
same script to fetch mod and
Le vendredi 15 février 2013 11:39:44, Christian JULLIEN a écrit :
Can you show me the content of config.mak? Especially, what is the value of
GCC_MAJOR and GCC_MINOR?
[cjullien@hilbert tinycc]$ more config.mak
# Automatically generated by configure - do not modify
prefix=/usr/local
Le vendredi 15 février 2013 13:39:57, grischka a écrit :
You wrote:
fixed pasto in in 108b2876; background for the additional $CC test is:
GCC_MAJOR may be set even is $CC not realy gcc (but i.e. clang, which (as
of 3.1) requires an addtional CFLAG to accept the non portable (gnuisms
all
Le vendredi 15 février 2013 14:49:09, Christian JULLIEN a écrit :
Thomas, your last commit lets Makefile find again GCC and now correctly
sets CFLAGS with warnings we want to ignore.
Christian
Not mine, Urs's.
Thomas
signature.asc
Description: This is a digitally signed message part.
Kysela
Joe Soroka
Kirill Smelkov
Luigi Rizzo
Manuel Simoni
Michael Matz
Milutin Jovanovic
mingodad
Nicolas Limare
Nikos Mavrogiannopoulos
Ramsay Jones
Romain Francoise
Roy Tam
Sam Watkins
Sergei Trofimovich
Sergey Vinokurov
Shinichiro Hamaji
Soloist Deng
Thomas Preud'homme
Timo VJ Lahde
Urs Janßen
Le vendredi 15 février 2013 19:14:23, Austin English a écrit :
This was around before 0.9.26, but I forgot to report it:
make[1]: Leaving directory `/home/austin/src/tinycc/lib'
./texi2pod.pl tcc-doc.texi tcc.pod
pod2man --section=1 --center= --release= tcc.pod tcc.1
texi2html
Le jeudi 14 février 2013 06:58:55, grischka a écrit :
Thomas Preud'homme wrote:
But no.
./configure --cc=tcc make
Ah yeah right. I was sure I saw a gcc flying around in lib/Makefile
recently. Maybe bad memory.
Flew away here: http://repo.or.cz/w/tinycc.git/commitdiff
Le jeudi 14 février 2013 12:52:13, grischka a écrit :
Thomas Preud'homme wrote:
Oh crap. Can you tell me whether there is still a libc.so.6 in /lib?
If yes, then I could replace the ldd call by something like ls
/lib/**/libc.so.6 (of course it would not be ** since it's not bourne
Greetings everybody,
Hopefully I pushed the last change to support multiarch setup. Please check
that tcc still builds correctly and that the resulting binary can create
working programs.
I already prepared locally the push for tagging 0.9.26 and changing the
version. Since so far you've been
Le jeudi 14 février 2013 16:06:24, Christian JULLIEN a écrit :
Sorry Thomas, made 5 mn ago
As I said, super fast testers :) Thanks !
As usual, I used a fresh git clone to test:
makeinfo tcc-doc.texi
make -C tests test
make[1]: Entering directory `/home/jullien/tinycc/tests'
Le jeudi 14 février 2013 16:26:28, Christian JULLIEN a écrit :
Sure,
jullien@sims ~ $ find /usr -name 'crti.o'
/usr/lib/arm-linux-gnueabihf/crti.o
Of course, how stupid I am ! Ok, so I can detect EABI easily but now I need to
find a way to detect whether it's standard softloat or hardfloat
Le jeudi 14 février 2013 16:43:13, Jerry Reed a écrit :
On Raspberry PI, configured --with-libgcc, getting this:
[SNIP]
So with or without libgcc, having trouble finding the crt* files.
Can you try again with the commit b4656f3191a9e26aa99a42f3b379a5e2c1451d51
included?
I might have
Le jeudi 14 février 2013 16:36:23, Jerry Reed a écrit :
Hi:
On the Raspberry Pi now:
After a git pull/configure/make clean/make:
pi@raspberrypi ~/tinycc $ make test
make -C tests test
make[1]: Entering directory `/home/pi/tinycc/tests'
hello-exe
../tcc -B..
Le jeudi 14 février 2013 17:08:15, Christian JULLIEN a écrit :
RPi is still OK, but now on CentOS, I get:
test3
../tcc -B.. -DTCC_TARGET_X86_64 -DONE_SOURCE -run ../tcc.c -B..
-DTCC_TARGET_X86_64 -DONE_SOURCE -run ../tcc.c -B.. -DTCC_TARGET_X86_64
-DONE_SOURCE -run
Le jeudi 14 février 2013 18:05:24, Christian JULLIEN a écrit :
This commit still works on RPi but produces
test3
../tcc -B.. -DCONFIG_LDDIR=\lib64\ -DTCC_TARGET_X86_64 -DONE_SOURCE
-run ../tcc.c -B.. -DCONFIG_LDDIR=\lib64\ -DTCC_TARGET_X86_64
-DONE_SOURCE -run
Le jeudi 14 février 2013 18:12:47, vous avez écrit :
./hello /lib/libgcc_s.so.1: error: bad architecture
Can you show me the output of find /lib -name libgcc_s.so.1?
Best regards,
Thomas
signature.asc
Description: This is a digitally signed message part.
Le jeudi 14 février 2013 23:17:14, Thomas Preud'homme a écrit :
Le jeudi 14 février 2013 18:12:47, vous avez écrit :
./hello /lib/libgcc_s.so.1: error: bad architecture
Can you show me the output of find /lib -name libgcc_s.so.1?
Best regards,
Thomas
Forget about it. I made a wrong
Le jeudi 14 février 2013 18:05:24, Christian JULLIEN a écrit :
This commit still works on RPi but produces
test3
../tcc -B.. -DCONFIG_LDDIR=\lib64\ -DTCC_TARGET_X86_64 -DONE_SOURCE
-run ../tcc.c -B.. -DCONFIG_LDDIR=\lib64\ -DTCC_TARGET_X86_64
-DONE_SOURCE -run
Le mercredi 13 février 2013 12:12:34, Thomas Preud'homme a écrit :
Le mardi 12 février 2013 19:28:16, Ramsay Jones a écrit :
Also we see:
$ ls -l /usr/lib/crt?.o
-rw-r--r-- 1 root root 2459 2007-04-04 11:31 /usr/lib/crt1.o
-rw-r--r-- 1 root root 2296 2007-04-04 11:31 /usr/lib
On Wed, 13 Feb 2013 14:33:46 +0100, grischka wrote:
Thomas Preud'homme wrote:
Here is a first version of the patch. Granted, detecting multiarch
at configure time and specifying the triplet in tcc.h is better but
the result is quite ugly for now.
What about adding a small C file that we
On Wed, 13 Feb 2013 08:30:14 -0700, arn...@skeeve.com wrote:
Thomas Preud'homme robo...@celest.fr wrote:
Why not but strike multiarch from that as I don't see how we could
detect it by compiling a C program.
Use the output of ldd to tell you where the C library is.
Yep true, I thought
Le mercredi 13 février 2013 17:16:28, Thomas Preud'homme a écrit :
On Wed, 13 Feb 2013 08:30:14 -0700, arn...@skeeve.com wrote:
Thomas Preud'homme robo...@celest.fr wrote:
Why not but strike multiarch from that as I don't see how we could
detect it by compiling a C program.
Use
Le mercredi 13 février 2013 19:08:37, Thomas Preud'homme a écrit :
Le mercredi 13 février 2013 17:16:28, Thomas Preud'homme a écrit :
On Wed, 13 Feb 2013 08:30:14 -0700, arn...@skeeve.com wrote:
Thomas Preud'homme robo...@celest.fr wrote:
Why not but strike multiarch from that as I don't
Le mercredi 13 février 2013 16:17:42, Thomas Preud'homme a écrit :
Ok, I can do that.
See attached patch and the diffstat below:
configure| 48 +---
print_env_info.c | 35 +++
2 files changed, 40
Le mercredi 13 février 2013 21:29:04, grischka a écrit :
Thomas Preud'homme wrote:
I suggest we include it and then release tomorrow once people checked I
didn't break something with my last patches.
+if ! $cc -o print_env_info print_env_info.c 2/dev/null ; then
echo big/little
Le mercredi 13 février 2013 21:39:07, Christian Jullien a écrit :
After git pull on RPi I get:
$ make make test
gcc -o libtcc.o -c libtcc.c -DTCC_TARGET_ARM -DWITHOUT_LIBTCC
-DTCC_ARM_EABI -DTCC_ARM_HARDFLOAT -DTCC_ARM_VFP -I. -Wall -g -O2
-fno-strict-aliasing -Wno-pointer-sign
Le mercredi 13 février 2013 22:18:37, Thomas Preud'homme a écrit :
Le mercredi 13 février 2013 21:39:07, Christian Jullien a écrit :
After git pull on RPi I get:
$ make make test
gcc -o libtcc.o -c libtcc.c -DTCC_TARGET_ARM -DWITHOUT_LIBTCC
-DTCC_ARM_EABI -DTCC_ARM_HARDFLOAT
Le mercredi 13 février 2013 21:39:41, Austin English a écrit :
On Wed, Feb 13, 2013 at 11:31 AM, Thomas Preud'homme robo...@celest.fr
wrote:
Le mercredi 13 février 2013 16:17:42, Thomas Preud'homme a écrit :
Ok, I can do that.
See attached patch and the diffstat below:
configure
Le mercredi 13 février 2013 23:02:48, grischka a écrit :
Thomas Preud'homme wrote:
Indeed, for now we already need gcc for compiling a few files in tcc.
But no.
./configure --cc=tcc make
Ah yeah right. I was sure I saw a gcc flying around in lib/Makefile recently.
Maybe bad memory
Le samedi 9 février 2013 16:06:31, Christian Jullien a écrit :
As with gcc or cl, could tcc -v show processor/system info ?
For example, something similar to
tcc –v
tcc version 0.9.25 – WIN32 x86
tcc version 0.9.25 – WIN32 x86_64
tcc version 0.9.25 – Linux ARM hard float
Does it give the
Le samedi 9 février 2013 23:14:46, Christian Jullien a écrit :
Does it give the target architecture or the host architecture?
It should return target, we generally know on which host we are running on
(useless yet can be added as well if you like)
Why not just use readelf or equivalent
Le vendredi 8 février 2013 09:36:44, Akim Demaille a écrit :
Something must have been changed in the way the out-of-tree
builds are handled. This used to work.
$ git describe --always
7a477d7
$ mkdir -p _build/gcc48
$ cd _build/gcc48
$ ../../configure CC=gcc-mp-4.8
configure: WARNING:
Le mercredi 6 février 2013 13:13:11, Christian JULLIEN a écrit :
Here are some benchmarks comparing tcc and gcc 4.7 on RPi.
Benchmarks are taken from my OpenLisp tests suite.
Source files for the bench consist of 15040 lignes of C code generated form
compiler
Was gcc compiling in -O0? If
Le lundi 4 février 2013 18:47:59, grischka a écrit :
Yes, just that it once worked for me before another real case
obviously won over mine.
In any case the
#ifndef CONFIG_LDDIR
clause in tcc.h now looks right which it didn't before.
Absolutely.
Anyhow. Maybe you might want to
Le mardi 5 février 2013 01:05:35, Daniel Glöckner a écrit :
Hi,
On Mon, Feb 04, 2013 at 01:47:46PM +0100, Christian JULLIEN wrote:
your mail client produced a multipart/alternative with an empty
text/plain part.
The error is in gfunc_prolog when it does
pn = (pn + (align-1)/4)
Le lundi 4 février 2013 20:51:29, grischka a écrit :
Thomas Preud'homme wrote:
1) too many warnings conversion from/to ptr - integer of different
size
http://repo.or.cz/w/tinycc.git/commitdiff/82bcbd027f100d7601c6139e93e1f6
9a 9cc46244
Why some uplong were replaced by uintptr_t
Le mardi 5 février 2013 20:41:59, Robert Clausecker a écrit :
Hello!
Today I tried to compile tcc (mob) with the clang compiler. I performed
the following steps [1] to compile tcc:
$ cd src/tinycc
$ ./configure --cc=clang --prefix=$HOME
$ make
Now I observe that gcc is
Le lundi 4 février 2013 07:46:08, Christian Jullien a écrit :
I'm still looking in ISO standard if there is a note on this conversion.
Anyway, tcc behaves differently from gcc (and *all* other compiler I know
where is conversion truncates) while tcc rounds
I've seen Daniel pushed a new commit
Le lundi 4 février 2013 17:34:28, grischka a écrit :
Thomas Preud'homme wrote:
If you want to keep the if structure you created, there should be a comma
so that each if is in the else clause of the previous one.
Yep, mistake. Fixed.
Because here multiarch
dir is tested only
Le lundi 4 février 2013 16:30:53, grischka a écrit :
Hi, I reinstalled my linux partitions and did run some tests.
My conclusions:
1) too many warnings conversion from/to ptr - integer of different size
http://repo.or.cz/w/tinycc.git/commitdiff/82bcbd027f100d7601c6139e93e1f69a
Le jeudi 31 janvier 2013 02:07:36, Domingo Alvarez Duarte a écrit :
Also here :
static void asm_expr_logic(TCCState *s1, ExprValue *pe)
{
int op;
ExprValue e2;
asm_expr_prod(s1, pe);
for(;;) {
op = tok;
if (op != '' op != '|' op != '^')
---BeginMessage---
As you are going to prepare a tcc release here are some notes (all based on
mob branch):
toplevel Makefile still has some hardcodd uses of gcc in it, but uses
$(CPPFLAGS) $(CFLAGS) - whenever one configures with a different compiler
(configure --cc=whatever) and that compiler
Le jeudi 31 janvier 2013 00:08:19, Ivo van Poorten a écrit :
Error:
$ ./configure --cc=tcc
Binary directory /usr/local/bin
TinyCC directory/usr/local/lib/tcc
Library directory /usr/local/lib
Include directory /usr/local/include
Manual directory/usr/local/share/man
Info
Le jeudi 31 janvier 2013 02:19:38, Domingo Alvarez Duarte a écrit :
Here is some that I found simple to make:
Author: mingodad mingo...@gmail.com 2013-01-31 01:17:50
Committer: mingodad mingo...@gmail.com 2013-01-31 01:17:50
Parent: 1b1e7ee1fd2f269872128dc5e8b830bd55dfa80c (Fix
Le jeudi 31 janvier 2013 12:34:27, Stephan Beal a écrit :
On Thu, Jan 31, 2013 at 12:07 PM, Thomas Preud'homme
robo...@celest.frwrote:
-strcpy(buf, __bound_);
-strcat(buf, name);
+snprintf(buf, sizeof(buf), __bound_%s, name);
strcpy
Le jeudi 31 janvier 2013 13:19:59, grischka a écrit :
Thomas Preud'homme wrote:
bcheck.o : lib/bcheck.c
- gcc -c $ -o $@ $(CPPFLAGS) $(CFLAGS)
+ $(CC) -c $ -o $@ $(CPPFLAGS) $(CFLAGS)
Unfortunetely it still breaks because of a wrong detection of GCC_MAJOR.
Because
Le jeudi 31 janvier 2013 12:57:28, Aharon Robbins a écrit :
Hi Guys.
Something broke really bad:
]$ cat hello.c
#include stdio.h
int main(int argc, char **argv)
{
printf(hello, world\n);
return 0;
}
$ tcc hello.c -o hello
In file included from hello.c:1:
In file
Le jeudi 31 janvier 2013 13:45:28, Domingo Alvarez Duarte a écrit :
Maybe you didn't noticed that snprintf guarantee no buffer overflow while
sprintf doesn't
I didn't. Grischka just explained how no overflow can occured so sprintf is
fine.
Thomas
signature.asc
Le jeudi 31 janvier 2013 14:53:42, grischka a écrit :
Thomas Preud'homme wrote:
Maybe we should just put bcheck.o into libtcc1.a (and thus make via
the rules of lib/Makefile). Unless there is a reason why we
shouldn't.
Yes but that doesn't change the general assumption that we
Le mercredi 30 janvier 2013 06:31:12, Christian Jullien a écrit :
Hi all,
The only very minor issue I had is that, by default, GNU time is not
installed on RPi this prevents test/speedtest to work.
Not really an issue I would say, it happens a lot to need additional
dependency to run a
Le samedi 26 janvier 2013 07:09:11, Feng Nauh a écrit :
tinycc/tests:
on archlinux x86_64, make weaktest, result as:
...
tcctest.c:391:5: note: use option -std=c99 or -std=gnu99 to compile your
code
make: *** [weaktest] Error 1
I think the weaktest is not included in the default tests
Hi there,
I think tinycc is ready for release now and I wanted to do it today before I
noticed that the Changelog is quite small considering all the time passed
since the last release. Hence I'm wondering if all the important bits are
mentionned there.
I'd thus like you to mention me any
Le mercredi 30 janvier 2013 19:00:43, grischka a écrit :
I did some cleanup. The idea is to make Changelog more interesting
and readable to the user.
Much better indeed. Thanks.
Also I made some few other changes. Please re-test configure and build.
Also with cross-compilers (configure
Should be fine now. Can Jerry and you try the fix I've just pushed in mob?
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
Thomas Preud'homme robo...@celest.fr wrote:
Jerry Reed irving2nd2...@gmail.com wrote:
Thank you so much for all your work, Thomas.
On the BeagleBone briefly. When I configure with
./configure
Then the tests fail like this:
Test: 11_precedence...
tcc: error: undefined symbol '__aeabi_idiv
Le dimanche 27 janvier 2013 14:07:19, vous avez écrit :
Thank you.
I will clone the repository again with -mob and test again.
Thanks. I appreciate any testing since I made a significant (not in terms of
line of code but in terms of possible regressions) change in the arm code
yesterday. It
Le dimanche 27 janvier 2013 15:52:55, vous avez écrit :
I can get a core file,but it is not very informative, at least to me. The
backtrace is only 3 entries, in hex, then a message duplicate
entries,possible stack corruption. This is what I got last night, need to
try again after the clone
Le dimanche 27 janvier 2013 15:59:48, Thomas Preud'homme a écrit :
Le dimanche 27 janvier 2013 15:52:55, vous avez écrit :
I can get a core file,but it is not very informative, at least to me. The
backtrace is only 3 entries, in hex, then a message duplicate
entries,possible stack
Le samedi 26 janvier 2013 02:25:53, Jerry Reed a écrit :
I would be happy to retest on the BeagleBone and the Raspberry Pi when a
relevant build is ready.
Fixed. Go ahead and try :)
Regards,
Jerry
Best regards,
Thomas
signature.asc
Description: This is a digitally signed message
Le jeudi 24 janvier 2013 11:35:30, Thomas Preud'homme a écrit :
I finally got around to look in this last failure. I just started but the
good news is that it's limited to the -run function. There is no problem
when compiling the example. Objdump shows it's the exact same code in both
case
Le vendredi 25 janvier 2013 18:53:28, Thomas Preud'homme a écrit :
The problem is that tcc, when linking, was copying the type for functions
symbol (STT_FUNC and STT_GNU_IFUNC) in the resulting executable.
I think I got how it works. The dynamic resolver works in 2 steps. First it
search
Le vendredi 25 janvier 2013 19:37:38, grischka a écrit :
Thomas Preud'homme wrote:
I just started but the
good news is that it's limited to the -run function. There is no problem
when compiling the example.
Ok got it. Fix attached.
diff --git a/tccelf.c b/tccelf.c
index da81d03
Le mercredi 23 janvier 2013 22:48:02, Thomas Preud'homme a écrit :
There is a failure after
that, but it looks like this:
gcc -o libtcc_test libtcc_test.c ../libtcc.a -I. -I/var/log/tinycc -Wall
-g -O2 -fno-strict-aliasing -Wno-pointer-sign -Wno-sign-compare
-DTCC_TARGET_ARM
Le lundi 21 janvier 2013 03:53:04, Jerry Reed a écrit :
Any further suggestions for how I might obtain more information here.
Can you try from a checkout of the tree as of commit
bfb00494eb2ffaf4fbf68a8ecabe9e503f4cdf65 ?
The change to introduce hardfloat calling convention also changed a
Le mercredi 23 janvier 2013 21:06:14, vous avez écrit :
Hi Thomas:
I will try that commit soon, maybe tonight EST.
In the meantime, I have uncovered a few more parameters of the problem.
Now tried it on a BeagleBone (TI OMAP Arm processor) instead of a Raspberry
Pi.
Le mercredi 23 janvier 2013 22:20:19, vous avez écrit :
Ok, hoping I did this correctly. I'm not very familiar with git, we use
svn.
git clone git://repo.or.cz/tinycc.git $HOME/build/tinycc
cd build/tinycc
git checkout bfb00494eb2ffaf4fbf68a8ecabe9e503f4cdf65
./configure
Le mercredi 23 janvier 2013 22:48:02, Thomas Preud'homme a écrit :
If yes, please attach the binary so that I can look at the generated code
*and* the output of the test which is in 40_stdio.test.
My mistake, the output is in 40_stdio.output
No need to do any of what I asked. The error is in the test itself:
As you said, the test runs as follows:
char inChar;
while ((inChar = fgetc(f)) != EOF)
//do something
The problem stems from the fact that fgetc returns an int, not a char. This is
for a very good reason: EOF is defined to
, ShowChar);
}
fclose(f);
loops forever.
Same here, it never worked on the hardfloat variant but it works like a charm
on the softflate. I should investigate this one as it's fully reproducible.
Thanks for your report.
Best regards,
Thomas Preud'homme
signature.asc
Description
201 - 300 of 466 matches
Mail list logo
