Michael Matz wrote:
On Sat, 15 Oct 2016, David Mertens wrote:
Ah, now I get errors running the preprocessor tests. Here's a
representative
result:
PPTest 14 ...
Yes. The whole commit range around there is a bit shaky. You need some
commits from after that one to get a better working comp
Hi,
on Github we could use Travis to run tests after every commit.
We could also use Qemu there to check if the other architectures still
work. It might also serve as an example how to setup a cross development
environment with TinyCC.
Best regards.
Daniel
I am less concerned about losing this kind of meta-info, as I expect we
would continue discussion primarily on the mailing list. Mailing lists seem
to me to be much better venues for discussion than the facilities provided
by github.
My bigger concern is: who would be the project managers? Who wou
Well, I’m not sure savannah allows this, but one way to limit anarchical and
gratuitous commits is to refuse (with help of a pre-commit hook, see
https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks) any commit that does
not refer to a ticket.
This way, when you want to do something you mus
On Sun, Oct 16, 2016 at 11:26 AM, avih wrote:
> > I am less concerned about losing this kind of meta-info, as I expect we
> would continue discussion primarily on the mailing list.
>
> Would you/we?
>
> The initial suggestion mentioned pull-requests as being easier to handle
> than discussing pat
Hey everyone,
I owe an apology to grishka. Grishka, I may not like how you currently
handle unwanted pushes (often by revert without discussion), but I don't
think you'd be half as reactive if we kept unwanted pushes out of the main
repo in the first place. In that case we'd get the best of your e
avih, one more note:
The big problem is not how we handle our discussions on the mailing list,
it's when a person does not respect the open source governance and pushes a
bunch of unsolicited commits without *any* discussion. This has happened
many times over the last three or four years. Pull req
Hi,
On Sun, 16 Oct 2016, Chen, Xianwen wrote:
I'm using the latest release, but not the latest version as of the
source code. Are you suggesting me to compile tcc itself from source
codes?
Yes.
Ciao,
Michael.
___
Tinycc-devel mailing list
Tinycc
Hi,
On Sun, 16 Oct 2016, avih wrote:
Overall, I'd vote to move tinycc to github, with the caveat that it'd be
nice to also have an external archive of all the discussions, issues,
reviews, etc.
You can't "move" tinycc anyway. If people want to start using github:
more power to them, repo.o
Hi,
On Sun, 16 Oct 2016, Christian Jullien wrote:
Ok Michael,
It is defined in sys/cdefs.h as:
#if __GNUC_PREREQ__(2, 7) || defined(__INTEL_COMPILER)
#define __dead2 __attribute__((__noreturn__))
#define __pure2 __attribute__((__const__))
#define __unused__attribute__((
Hi,
On Mon, 17 Oct 2016, Michael Matz wrote:
Now, I do agree that we'd want to add a work around for this in tcc. I
think a better work-around than defining __GNUC__ is to define the above
macros instead. __GNUC__ simply has quite some side-effects. (E.g.
after the patch you can't compile
Hello Michael,
On Sun, Oct 16, 2016 at 5:59 PM, Michael Matz wrote:
>
> You can't "move" tinycc anyway.
>
Of course not. There are only a handful of folks who really understand the
inner workings of tcc (you being one of them), and if they want to stick
with repo.or.cz, then that's where code
Thank you Michael,
Trying your latest commit makes me able to compile and run all tests except
those below.
Even a very simple test fails to find stdlib:
$ pwd
/usr/home/jullien/tinycc
$ cat foo.c
#include
int main()
{
printf("Hello World\n");
return 0;
}
$ ./tcc -B. foo.c -o hello
tc
Having only a look at tccgen.c I see #if related to an architecture (which
is of course Ok) but but more and more often
#if defined(TCC_TARGET_ARM64) || defined(TCC_TARGET_X86_64)
.
#else
#endif
Which are used to generate code related to word / int / long / long long
processor size.
I
This morning, it was on FreeBSD x64, nox testing on i386 gives me a different
result with again __aligned issue.
../tcc -B.. -I../include -I.. -I.. -DTCC_TARGET_I386 -DONE_SOURCE -run ../tcc.c
-B.. -I../include -I.. -I.. -DTCC_TARGET_I386 -DONE_SOURCE -run ../tcc.c -B..
-I../include -I.. -I.. -
15 matches
Mail list logo
