tinycc-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tinycc-devel] [ARM regression] ret_longdouble_test2... failure


From: Thomas Preudhomme
Subject: Re: [Tinycc-devel] [ARM regression] ret_longdouble_test2... failure
Date: Wed, 14 May 2014 23:40:04 +0800
User-agent: Roundcube Webmail/0.7.2

Le 2014-05-13 23:29, jiang a écrit :


--- a/tests/Makefile
+++ b/tests/Makefile
@@ -207,8 +207,8 @@ asmtest: asmtest.ref
  abitest-cc$(EXESUF): abitest.c $(top_builddir)/$(LIBTCC)
$(CC) -o $@ $^ $(CPPFLAGS) $(CFLAGS) $(NATIVE_DEFINES) $(LIBS) $(LINK_LI

-abitest-tcc$(EXESUF): abitest.c libtcc.c
- $(TCC) -o $@ $^ $(CPPFLAGS) $(CFLAGS) $(NATIVE_DEFINES) -DONE_SOURCE $(L
+abitest-tcc$(EXESUF): abitest.c $(top_builddir)/$(LIBTCC)
+ $(CC) -o $@ $^ $(CPPFLAGS) $(CFLAGS) $(NATIVE_DEFINES) $(LIBS) $(LINK_LI

  abitest: abitest-cc$(EXESUF) abitest-tcc$(EXESUF)
         @echo ------------ $@ ------------

Where does this change come from? I hope you don't intend to commit this. The purpose of abitest-tcc is to be compiled by tcc, not by the host compiler $(CC).

I still didn't look at anything that happen since 2ac238f but given the recent breakage I'll try to take a look at some point (but still can't right now). However the number of changes is pretty big and difficult to read now. The other solution would be to just do a git diff between then and now. Given the terse changelog it might not make a big difference anyway. Please be more specific when you commit something, instead of just "fix commit foo".

Cheers,

Thomas



reply via email to

[Prev in Thread] Current Thread [Next in Thread]