[Tinycc-devel] Still waiting for a release. How can we help?

Hi grischka. We are still waiting for a release. What can we do to help you? Please let us know. The tinycc repo has again some ugly tags, that need an urgent cleanup. -- Regards ... Detlef ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org htt

Re: [Tinycc-devel] crt1.o not found

Hi Brian > > On unix, multiple search directories use the colon ":" as separator > That was my mistake, heheh for some reason I thought I had to use > commas. Thanks a lot, it worked! Great. > Speaking of tcc's internals, what is actually needed in order to run > it? > I compiled it statically s

Re: [Tinycc-devel] crt1.o not found

Hi Brian.tcc can't find the files, because you build your tcc with broken search path.On unix, multiple search directories use the colon ":" as separator(try: echo $PATH)and tcc uses the same style.When you configured multiple directories for tcc,they are printed on separate lines with "tcc -vv".Ad

Re: [Tinycc-devel] __VA_OPT__

> How do we feel about the lack of __VA_OPT__?I would delay that after the release.@grischka, your ping for a release.-- Regards ... Detlef ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Re: [Tinycc-devel] RFC: Colored warnings/errors ?

tcc should be as small an simple as possible,so i vote against any colored output.For colored output, i pipe the output through a script.I use "colormake.pl" here and to reduce typing, i use a link with the shorter name "cmpl".Oh, i changed my "colormake.pl" to recognice tcc / *tcc.-- Regards ... D

Re: [Tinycc-devel] new backend

Hi PaulCan you please tell me more about the new backend,which you are working on?Either here or with private mail.Thanks.> Well somewhere along the way I fixed it > when I started making gjmp and gjmp_append return sane values. Great > Are there any docs out there that describe how to write a ba

Re: [Tinycc-devel] Re: Waiting for a release / Please delay any commits

>> We have the tinycc 0.9.28 release canditate for a long time,>> but still no release@grischka, we need you>> Savannah has a buglist for tinycc:>> https://savannah.nongnu.org/bugs/?group=tinycc>> It works for collecting issue,>> but unfortunately no one works on this issue list> I did not even kno

Re: [Tinycc-devel] Waiting for a release / Please delay any commits

Hi Ekaitz>> My suggestions:>> * Please hold back any commit before the release.>> * If you think, you have an urgent change to fix an urgent bug,>> discuss it on the mailing list first.>> * Together, we decide, if we postpone the change after the release is out,>> or commit the fix before the relea

[Tinycc-devel] Waiting for a release / Please delay any commits

We have the tinycc 0.9.28 release canditate for a long time,but still no release.All people here can help grischka to be more confident to make a release.My suggestions:* Please hold back any commit before the release.* If you think, you have an urgent change to fix an urgent bug, discuss it on th

Re: [Tinycc-devel] Questions about the future of TinyCC

Hi César Welcome to TinyCC> Basically, what I need is just a C compiler.> Written in C. A good C compiler. It depends, what you define as a 'good' compiler.TinyCC is a single pass compiler and very good at compilation speed.The code created by TinyCC is often remarkable slower,compared to code crea

[Tinycc-devel] NotABug (Report a Bug about Parsing #ifdef, #ifndef and #else Line)

Am 31.03.24, 17:45 schrieb 837806295 via Tinycc-devel :Hi 837806295.Using a name for communication is better...> Hello!> Report a Bug about Parsing #ifdef, #ifndef and #else Line.Your intention to write a bug rebort is good,but your example is not vaild C code.From your example:> { > #ifndef Test

Re: [Tinycc-devel] Waiting for release...

Am 24.03.24, 16:53 schrieb "codif...@gmail.com" :> "release" personally I've just tracked git master (or is it main these days?) > and pull roughly monthly, > maybe I just got lucky, but its always "just works" (tm)Yes, using the mob branch is good (most of the time),but the tcc version in various

Re: [Tinycc-devel] recent riscv changes

Hi @ekaitz>> For adding new features, a message to the mailing list is always better.> I wasn't sure about that so I just decided to send the changes. > You are right.It is always a good idea,but very important during the rc phase.> Now that we are in the mailing list, > I have some support for ext

[Tinycc-devel] Waiting for release...

Hi grischka.When do you plan to do a release?What can we, to help you?-- Regards ... Detlef ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel

[Tinycc-devel] issue in the recent riscv change, which added the ".option" asm directive

Welcome to tinycc and thanks for your recent riscv-changes @Ekaitz.All are waiting for a release and should avoid to add new features.Since your changes are only for riscv targets, i hope, that the changes would not delay the release of tcc 0.9.28 even further,(but only @grischka can make a release

[Tinycc-devel] Recent patches for the TinyCC 0.9.28 Release Candidate

Hi TinyCC follower. The current branch is a release candidate for TinyCC 0.9.28 since some month. From the active people here, only grischka has the rights to make a release, and I suggest, that we should help him to be comfortable to make a release by: * more testing * add only minimal fixes to

Re: [Tinycc-devel] SIMD intrinsics

Am 15.01.24, 08:57 schrieb Mathias Widman :> I am new to the list so forgive my lack of knowledge of previous questions.Welcome here, Mathias.> I wonder if there are any plans on incorporating/supporting SIMD intrinsics.Which target processor / which intrinsics?intrinsics

Re: [Tinycc-devel] Any plans to support utf8/utf16 string literals?

Am 15.01.24, 08:27 schrieb Brad Robinson via Tinycc-devel :> Just wondering if there are any plans to add support for utf8 (aka u8"string")> and utf16 (aka u"string") string literals in tcc?I also would like this c11 feature to be supportedand I have an old patch to detect thisbut it is not used in

[Tinycc-devel] incomplete searchpath for i386-tcc

anager in /usr/lib/i386-linux-gnu/libcurses.soOn my xubuntu, the installed package is: libncurses-dev:i386 I used the example from "Writing Programs with NCURSES"(ncurses-intro.pdf) in the section "Using the library"Am 06.01.24, 13:53 schrieb grischka via Tinycc-devel : On

Re: [Tinycc-devel] Re: Outdated tcc: Major bug in the pow function resulting in: 0.993013 = 0.860892

via Tinycc-devel : On 06.01.2024 01:10, Detlef Riekenberg via Tinycc-devel wrote: > > Of course, there might be more issues in 0.9.28rc > As example, "i386-tcc" on a x86_64 linux machine > is missing additional search dirs: Can we see the o

[Tinycc-devel] Outdated tcc: Major bug in the pow function resulting in: 0.993013 = 0.860892

Hi Aurélie TissonThanks for your report.This was fixed at least more than 52 month ago.(I tried tcc 0.9.27+git20200815.62c30a4a,and that version works without issues)Others have also already tested your exampleals also discovered, that this is fixed.Currently, we have a tcc 0.9.28rc and waitin

[Tinycc-devel] fixed in mob: Do not load all referenced libraries when linking a library

After your suggestions and comments, i pushed an updated fix for the build break of netbsd-curses to mob. Thanks ! Build times (best of 3) for "netbsd-curses" on my machine (64bit linux) The project build times include: * generating terminfo hash * generating compiled terminfo descripti

[Tinycc-devel] Do not load all referenced libraries, when linking a library

to not push my patch to mob. It would be nice, if you help with testing. -- Bye bye ... Detlef From 95045ae2407ab8070fd06810a6c97de21559c77c Mon Sep 17 00:00:00 2001 From: Detlef Riekenberg Date: Wed, 4 Oct 2023 22:48:48 +0200 Subject: [PATCH] tccelf: Do not load all referenced libraries when

Re: [Tinycc-devel] tcc 0.9.28rc testing: bug in autoconf 2.71 with AC_CHECK_DEFINE

> > On 24/9/23 11:03, Nick Bowler wrote: > >> The word AC_CHECK_DEFINE is not found anywhere in the Autoconf > >> source code or documentation. > > > > My guess would be that the 3rd party is the autoconf archive because > > they provide both AX_CHECK_DEFINE and AC_CHECK_DEFINE > > > > http://git.s

Re: [Tinycc-devel] tcc 0.9.28rc testing: bug in autoconf 2.71 with AC_CHECK_DEFINE

Thanks Nick and Peter for your analysis. Yes, the "AC_" prefix fooled me, that AC_CHECK_DEFINE belongs to autoconf. > On 2023-09-23, Nick Bowler wrote: > > On 2023-09-23, Detlef Riekenberg wrote: > >> AC_CHECK_DEFINE(__unix, CFLAGS="-DFOUND__unix $CFLAG

[Tinycc-devel] tcc 0.9.28rc testing: bug in autoconf 2.71 with AC_CHECK_DEFINE

Hi autoconf team. During testing of tcc 0.9.28rc, I found a strange bug in autoconf 2.71 with `AC_CHECK_DEFINE` for `__unix__`. For comparsion, i added checks for "__unix" and "__linux__": Overview: * [__unix__] always found, but the log text is crippled * __unix__ never found and the log text

Re: [Tinycc-devel] rc testing with netbsd-curses: build break

> >> Obviously when loading a .so library, > >> tcc additionally is loads its dependencies too. > > > > That would be correct, when the target is TCC_OUTPUT_MEMORY > > but i think, in all other cases, tcc should not do that. > > I'd suggest to use "grep -nrw tcc_load_dll ." for example. There is

Re: [Tinycc-devel] rc testing with netbsd-curses: build break

-- Bye bye ... Detlef > > libcurses/libcurses.so: error: referenced dll 'libterminfo.so' not found > > make: *** [GNUmakefile:529: libpanel/libpanel.so] Fehler 1 > > * libpanel/libpanel.so depends on libcurses/libcurses.so > > * libcurses/libcurses.so depends on libterminfo/libterminfo.so > > *

[Tinycc-devel] Fw: TCC 0.9.28rc testing: dte (updated)

Sorry, forget the compile time tests. There was sill an "-O2" active. > Results for testing 0.9.28rc with the project > https://github.com/craigbarnes/dte > > * build break > -> fixed in mob > > * 128 warnings: assignment from incompatible pointer type >-> that's ok. The project source has

[Tinycc-devel] TCC 0.9.28rc testing: dte

Results for testing 0.9.28rc with the project https://github.com/craigbarnes/dte * build break -> fixed in mob * 128 warnings: assignment from incompatible pointer type -> that's ok. The project source has macros to disable these warnings for gcc and clang * 1 warning: function might

[Tinycc-devel] rc testing with netbsd-curses: build break

For testing the tcc rc, i tried https://github.com/sabotage-linux/netbsd-curses: CC="tcc" make Build breaks with tcc for "libpanel/libpanel.so" (gcc works): tcc -v -shared -o libpanel/libpanel.so libpanel/_deck.lo libpanel/above.lo libpanel/below.lo libpanel/bottom.lo libpanel/del.lo libpanel/g

Re: [Tinycc-devel] Re : Lock-free tcc

My Wishlist / Roadmap for 1.0 Since we have now 0.9.28rc ( thanks for that, grischka), i want to write down my wishlist / roadmap for a future 1.0 release and ask you for improvements / comments. ( I have not added any issue/enhancement request to the bugtracker at savannah yet. ) ## Fix / Up

[Tinycc-devel] Es Eilt sehr / Very urgent: Bad tags on the tinycc project page

Hi grischkathanks for the 0.9.28rc, I will test it as much as possible.But please:* check and remove the bad tags from the repo.or.cz project pageSome tags are really bad.I hope, that you can delete them as project admin,without additional help of repo.or.cz-- Regards ... Detlef

Re: [Tinycc-devel] Relative paths of include files are not normalised, which can break #pragma once

Hi Herman > > On 25.06.2023 20:30, Herman ten Brugge via Tinycc-devel wrote: > >> > >> I just pushed a patch to fix this. > > > > Hi Hermann, > > > > some numbers from Win32: > > > > before: > >   # 6.334 s, 85768 lines/s, 27.9 MB/s > > after first patch: > >   # 11.825 s, 45941 lines/s, 14.9 MB/s

[Tinycc-devel] Please do a 0.9.28 release.

Hi Grishka.Please create a 0.9.28 release.Afterwards, we can work towards a 1.0.0 release, probably in this year.I hope, that we get more attention with a 0.9.28 releaseand maybe also new contributions/testers.Thanks for your effort. ___ Tinycc-devel mai

[Tinycc-devel] Has someone a Windows on ARM machine for a test?

tcc is using IMAGE_FILE_MACHINE_ARM (0x1c0) in tccpe.c.I expect, that this works since Windows CE,but can someone with a recent Windows (10/11 on ARM) system please check and report back herewhat the os files use and that a tcc compiled buinary works.```Microsoft documents also IMAGE_FILE_MACHINE

[Tinycc-devel] Another crash for a yarpgen1 testcase: seed 1988

Current tcc has still a problem for a yarpgen_v1 testcase (using seed 1988) Initialization works, but the program crash in the function tf_0_foo(). Output, when compiled with "-b -bt": func.c:344: at tf_0_foo: RUNTIME ERROR: division by zero driver.c:885: by main Stripped down source is attache

[Tinycc-devel] Crash for yarpgen_1 with seed 319: fixed in mob

> I tested tcc (mob:ef3eb02) with yarpgen v1 for seeds upto 999 > and found only one failure (seed 319): > > tcc (mob:ef3eb02) created a program, which segfaults when running. > > Building with "-bt -v" and running produced: > $ tst-O0 > func.c:4286: at tf_3_foo: RUNTIME ERROR: invalid memory ac

[Tinycc-devel] Overview for ubuntu, wich package provides which file.

I found this web page: https://packages.ubuntu.com/search?mode=exactfilename&suite=lunar§ion=all&arch=any&lang=en&keywords=crt1.o&searchon=contents -- Bye bye ... Detlef ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org

[Tinycc-devel] Help needed, where to find libc startup/runtime files

Hi. In order to help grishka to fix i386-tcc on a x86_64 linux machine, we should collect infos, where the startup/runtime files are located. On my machine (xubuntu 23.04: lunar): The libc can be found here: dpkg -S libc.so | grep 86 | sort libc6-amd64-cross: /usr/x86_64-linux-gnu/lib/libc.so

[Tinycc-devel] All known yarpgenv1 bugs fixed.Thanks Michael and Herman

Thank you so much, Michael and Herman for fixing the remaining yarpgen(v1) bugs,which i found with my testscript so far. (yarpgen.sh)The yarpgen.sh testscript was born out of my csmith testscript (csmith.sh).For your Info: I patched yarpgen, to generate the tons of printf on request.(Pull request

[Tinycc-devel] Another bug in tcc: Wrong array initialization (yarpgen.v1)

I added another tcc bug report, discovered by yarpgen (v1).https://savannah.nongnu.org/bugs/?63895Initialization of an array (of struct tf_3_struct_2) is broken.tf_3_struct_2 contains some structs of type tf_3_struct_1and tf_3_struct_1 contains bitfields and non bitfield member,and tcc always fail

[Tinycc-devel] Bug 63816 fixed (yarpgen_v1). Thanks Michael

Thanks Michael.Your commit c771cb52 fixes a lot of bugs in the yarpgen v1 generated tests.For seed values from 1 to 99, only 4 result failures left: 26, 56, 64 and 84.For 100 to 200, there are some more result failures (102, 117 and 173)and some compile aborts: 123, 143, 197.-- bye bye ... Detlef

Re: [Tinycc-devel] Re: Cross compiling for riscv64 on arm64

For tcc, it should make no difference in the code, if your system is a x86_64 or an aarch64 machine,but i expect, that tcc on aarch64 is far less tested.And yes, an full assembler for riscv64 is missing in tcc.For your issues with the missing "crt1.o" and "crti.o" files:These are the startup f

Re: [Tinycc-devel] tcc latest version and new glibc

Hi grischka.Another case, where the latest release makes problems,but current mob works.You said and did nothing about releasing a 0.9.28 from current mob and prepare for a 1.0 release.I already asked some month ago for a release.You also said and did nothing to fix the link issue for i386-t

Re: [Tinycc-devel] FWD: Can't build for riscv64 or arm64

Hi Sagar tcc has no support for 128bit int types. __uint128_t __int128_t You might try with a replacement (typedef struct with 2x uint64) This should be at least enough for the structsize for the typedef in signal.h, but acessing the elements in the code you try to compile will propably fail --

[Tinycc-devel] C standards committee

Hi JeanHeydI'm tracking c23 and we already exchanged some mails last autum.There are also bug reports for the open issues i send to you.tcc status, without additional testing( see http://www.github.com/winspool/stdtests )c99: complex missing (but that's allowed since c11 with the define)c99: _Pragm

[Tinycc-devel] supported newer std c features in tinycc

Oh, we also support the c11 variant of* _Static_assertthe upcoming c23 update makes the messagein _Static_assert optional. That should be easy to support-- Regards, Detlef ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mai

Re: [Tinycc-devel] Re: commit e5eedc0cd

Hi grischka.At the moment, i find nothing, what is required in /libto build i386 software on x86_64,but only things for running software.But that case must be handled by the compiled software.Can you please make a 0.9.28 release in the near future?That allow linux packages a far more current packa

[Tinycc-devel] commit e5eedc0cd

Hey grischka.Reducing the search path is a good idea. Thanks for that,but your code does not work for the i386-tcc on x86_64-linux.The path are different, as cross dev packages install files in:lib:/usr/lib/i386-linux-gnu/usr/libinclude:/usr/include/i386-linux-gnu/usr/includecrt:/usr/lib/i386-linux

[Tinycc-devel] VLA support is not detected with autoconf

tcc can't compile the attached VLA check (gcc works) and configure adds "#define __STDC_NO_VLA__ 1" to config.h The code was generated using the autoconf macro "AC_C_VARARRAYS". console output: tcc -std=c11 vla_conftest.c -c vla_conftest.c:30: error: constant expression expected Any ideas, ho

[Tinycc-devel] Fix for -gdwarf

tcc -gdwarf did not work as expected. When tcc was compiled without DWARF as default (--dwarf=5 as example), then DWARF_VERSION is 0, the -gdwarf command line option did not changed s->dwarf and tcc created stabs debug infos. I pushed a fix. Now, tcc does the same as gcc with "-gdwarf": dwarf-2

[Tinycc-devel] Our __has_include implementation needs a fix

We detect and handle "__has_include" (yeah), but it's broken (we return always 1) and we should fix it. Any ideas? __has_include was an gcc/clang extension, but it's now a part of C23. (change accepted in aug/sep 2021) The support for __has_include is also mentioned in an ISO document: https://w

Re: [Tinycc-devel] Broken commit e460f7dbb216

Hi grischka. > Please try to be more precise. > Also, the "(n > 1) &" part that you added in your one-line patch > > - if (n <= 0 || (n & (n - 1)) != 0) > + if (n < 0 || ((n > 1) & ((n & (n - 1)) != 0))) > > is just redundant. Yes, sorry for that. I pushed a cleanup and check my patch

[Tinycc-devel] Next failure with autotools: _Static_assert

With my patch for _Alignas, tcc works for the next two configure tests: A simple _Static_assert and _Noreturn check. But then tcc fails, and i have no idea, where to look: A _Static_assert in a struct. Any Ideas, how to fix that? code from a configure script, generated by GNU autoconf_2.71:

[Tinycc-devel] Tests for _Alignas (new autotools)

ched are a patch for the additional tests to verify my implementation changes for _Alignas. -- Bye bye ... Detlef From edb7f281c4a44654de6984bf35a3e1515865a1c0 Mon Sep 17 00:00:00 2001 From: Detlef Riekenberg Date: Thu, 28 Jul 2022 18:39:56 +0200 Subject: [PATCH 1/1] Tests for _Alignas(0), _Align

[Tinycc-devel] Broken commit e460f7dbb216

Hi grischka. After your commit related to CONFIG_TCC_CROSSPREFIX, every compiler failed to work on Linux. I rechecked with a clean checkout. Broken commit: https://repo.or.cz/tinycc.git/commitdiff/e460f7dbb2165112bc618816ec15be312b257de2 Message examples: repo.or.cz_tinycc$ ./tcc helloworld.c -o

[Tinycc-devel] new tcc release

The last tcc release is very old, and tcc has received many fixes and new features since then.What are the plans for a new release?I vote for a 0.9.28 rc with the current features, see, what simple fixes are possible and then make a release in the next weeks.(Would help distros to include a recent

[Tinycc-devel] bug: nolibc.h does not work with tcc

nolibc.h looks nice and we should support it.What is nolibc.h?a header to replace libc on linux with syscalls.created by Willy Tarreau (linux kernel 2.4 maintainer).Where?a single file version (changed 21.1.2021) is on his homepagehttp://git.1wt.eu/git/nolibc.git (License: MIT)The included test 'h

[Tinycc-devel] Reverted commits

Yes, that sounds resonable.I will ask here for comments for some patches(in new mails),and only commit the bug fixesRegards ..Detlef--Diese Nachricht wurde von meinem Android Mobiltelefon mit WEB.DE Mail gesendet. ___ Tinycc-devel mailing list Tinycc-dev

[Tinycc-devel] Reverted commits

Hi List. My commits from the last 2 month where reverted. Why? And why without any comment? Fixing simple bugs to make tcc more usable for all developer should be our goal. * Example Bug fixed, but patch reverted: * CC=tcc configure This is no longer possible *Example Bug fixed, but patch re

Re: [Tinycc-devel] [Fwd: bug in tcc wi32]

On Sa, 2010-05-01 at 13:58 +0200, grischka wrote: > Detlef, please fix. > > (Beware, not as suggested below ;)) > > --- grischka Opps. Sorry for that Problems. I take a look. -- By by ... Detlef ___ Tinycc-devel mailing list Tinycc-devel@nongnu.

[Tinycc-devel] Drop mercurialtcc [TinyCC on Mercurial]

On Di, 2007-11-13 at 14:04 +0800, KHMan wrote: > Hi all, > > "mercurialtcc" has been accepted on ShareSource. The URL is: > > http://sharesource.org/project/mercurialtcc/ In the old CVS-Only live of tcc, the inofficial mercurial tree was created. We have the git tree now, so I like to drop

Re: [Tinycc-devel] Need help with hardware i/o

On Do, 2009-08-20 at 22:04 -0700, live...@hotmail.com wrote: > I just discovered Tiny C Welcome, person without a name. > MS 'QuickC for DOS' had the inp()/outp() > functions defined in conio.h to do this. There is no support for a 16Bit DOS target in tinycc. > I can't figure out how to do th

tinycc.git (was: Re: [Tinycc-devel] Re: global 64-bit variables initialization)

On Mi, 2008-11-26 at 16:08 +, Joshua Phillips wrote: > Whatever happened to mercurialtcc on sharesource? I never used hg before. A while ago, I joined that tree and tried to sync patches from CVS, but due to real life, i'm unable to sync it to a usable sate. I suggest: rm -f > > We are since r

Re: [Tinycc-devel] Release Candidate - please test

On So, 2008-03-09 at 21:26 +0300, Alexander Gladysh wrote: > -#if !defined(__FreeBSD__) && !defined(__DragonFly__) && ! > defined(__OpenBSD__) > +#if !defined(__FreeBSD__) && !defined(__DragonFly__) \ > + && !defined(__OpenBSD__) && !defined(__APPLE__) > #include > #endif We really should test

Re: [Tinycc-devel] Release Candidate - please test

On Sa, 2008-03-08 at 22:52 +0100, grischka wrote: > Here are the file that I propose for release: I did not test the files yet, but I think that a regular release is much better. IMHO, the new tools should be usable in both environments (win32 and unix) to allow tcc as drop-in for gcc and mingw.

Re: [Tinycc-devel] Worm virus

On Mo, 2008-01-21 at 14:34 -0800, Gary Dumer wrote: > All of the EXEs were created with TCC from CVS for WindowsXP. > > Gary Dumer wrote: > AVG antivirus is detecting a WORM virus in all the EXEs > on my WindowsXP. > I'm using a recent version of TCC.Ummm... what does > it have to do with

[Tinycc-devel] mercurialtcc updated: Sync from cvs to hg (part 1)

As a step to sync mercurialtcc ( http://hg.sharesource.org/mercurialtcc ), here is an Overview of recent CVS commits by grischka: 1) 30.Oct.2007 http://lists.nongnu.org/archive/html/tinycc-devel/2007-10/msg00076.html Fix 'invalid relocation entry' problem on ubuntu - from Bernhard Fischer (from hg

[Tinycc-devel] mercurialtcc updated: Sync from cvs to hg (part 1)

As a step to update mercurialtcc, here is an Overview of recent CVS commits by grischka: 1) 30.Oct.2007 http://lists.nongnu.org/archive/html/tinycc-devel/2007-10/msg00076.html Fix 'invalid relocation entry' problem on ubuntu - from Bernhard Fischer (from hg) 2) 14.Nov.2007 http://lists.nongnu.org

__STDC_VERSION__ is needed (Re: [Tinycc-devel] CVS Sync - The Rest)

On So, 2007-12-16 at 20:02 +0100, grischka wrote: > I will drop those labeled > "[N] will not apply" > unless someone can tell a good reason why we would need one. > [N] 477 RL_tcc_defines_stdc_ver (c99) > http://hg.sharesource.org/mercurialtcc/rev/1e81d5b65878 every source, that

[Tinycc-devel] PATCH for CVS: remove unneeded swap in gen_opic()

no swap needed (we do not use c1 or l1 below) -- By by ... Detlef Index: tcc.c === RCS file: /sources/tinycc/tinycc/tcc.c,v retrieving revision 1.193 diff -u -r1.193 tcc.c --- tcc.c 19 Dec 2007 17:36:43 - 1.193 +++ tcc.c 13

[Tinycc-devel] hg: partial disable commit 496 (check for duplicate parameter)

This patch deactivates the detection of duplicate parameter and mercurialtcc can compile merucialtcc again. Does anyone has an idea for a real fix? Any comments about revert the complete commit? -- By by ... Detlef diff -r 062087f616c1 tcc.c --- a/tcc.c Sun Dec 02 20:00:05 2007 +0800 +++

[Tinycc-devel] mercutialtcc

On Fr, 2007-12-14 at 20:12 +0800, KHMan wrote: > that leads us to my usual ad: > maintainers/owners wanted for the Mercurial repository of tcc. :-) I'm interested, but i'm using git for other things. hg is new for me. tcc is still not self-contained: - the STDC - headers (in /usr/include) are n

[Tinycc-devel] PATCH: Do not define "linux" when the target is windows

When we build tcc on linux for TCC_TARGET_PE, the current code defines __linux__ "linux" is the wrong namespace (not defined in ansi mode: gcc -ansi *) -- By by ... Detlef Index: tcc.c === RCS file: /sources/tinycc/tinycc/tcc

[Tinycc-devel] cvs does not build: with fix for missing _WIN32 (resend)

Current cvs does not build on unix (normalize_path is only present in Windows) This is a resend Please tell me, what's wrong with this Patch. -- By by ... Detlef Index: tcc.c === RCS file: /sources/tinycc/tinycc/tcc.c,v retri

[Tinycc-devel] mercurialtcc is unable to rebuild tcc

I can compile the current mercurialtcc with gcc, but the resulting binary is unable to rebuild tcc: src/tcc/src$ ./gcc-2-tcc tcc.c -o tcc2 -ldl In file included from tcc.c:21: In file included from tcc.h:30: /usr/include/stdlib.h:757: redefinition of parameter '' Any ideas ? -- By by ...

Re: [Tinycc-devel] Current cvs does not build (_WIN32 missing) Here is a fix.

On Do, 2007-11-29 at 14:04 +0800, KHMan wrote: > > WIN32 is not defined on all Windows Compilers (PellesC as example), > > so i decided to use "_WIN32", as documented on msdn: > > ( http://msdn2.microsoft.com/en-us/library/b0084kay(VS.80).aspx ) > > I'll await comments. SDL does it like this: > >

Re: [Tinycc-devel] [BUNDLE] Eliminate many bogus warnings produced during compilation of tcc by gcc

On Do, 2007-11-29 at 09:19 +, Joshua Phillips wrote: > Once they go into http://hg.sharesource.org/mercurialtcc/, you can get > it from there. I downloaded the mercurialtcc 2 days ago, but the above commit was not visible in the web-interface and "hg log" is broken on Ubuntu Dapper: ... F

Re: [Tinycc-devel] [BUNDLE] Eliminate many bogus warnings produced during compilation of tcc by gcc

On Di, 2007-11-27 at 17:33 +, Joshua Phillips wrote: > Patch by David Wheeler; I've committed it to the "incoming" branch. > (unpack using "hg unbundle ...") Can you please post patches to the List in a human readable format ( == text only)? Thanks. -- By by ... Detlef _

[Tinycc-devel] size and speed test

With my previous Patch and 2 additional changes, i can compile tcc with PellesC --- -#ifndef __GNUC__ +#if !defined (__GNUC__) && !defined(__POCC__) and -#warning add arch specific rt_get_caller_pc() +// #warning add arch specific rt_get_caller_pc() --- I used the stripped tcc binaries to com

[Tinycc-devel] Current cvs does not build (_WIN32 missing) Here is a fix.

A current commit added "normalize_slashes()", but this call in tcc_open() was not protected with _WIN32 WIN32 is not defined on all Windows Compilers (PellesC as example), so i decided to use "_WIN32", as documented on msdn: ( http://msdn2.microsoft.com/en-us/library/b0084kay(VS.80).aspx ) --

[Tinycc-devel] cvs does not compile: (Import more changesets from Rob Landley's fork - part 2 )

On Mi, 2007-11-21 at 17:16 +, grischka wrote: > CVSROOT: /sources/tinycc > Module name: tinycc > Changes by: grischka 07/11/21 17:16:32 > > Modified files: > . : Changelog Makefile stddef.h tcc.c tccasm.c >tccelf.c tcctok.h > win3

Re: [Tinycc-devel] Win32

On Di, 2006-09-12 at 14:50 +0100, Eric Chubb wrote: > Yes, I tried linking to that library but the compiler seems to treat the > library > argument as a filename, > tcc: cannot find -lC:\tcc\lib\KERNEL32.lib tcc needs a simple "*.def" - File and in /win32/lib/ are only old versions for kernel32