Vincent Lefevre wrote:
>
> But my point is that with the above testcase, you cannot know whether
> the difference between gcc and tcc comes from strtod (which would be
> valid, as strtod doesn't specify the sign or NaN) or the "d = -d;"
> (which would be invalid). A printf should have been added
On 2021-01-04 04:59:28 +0100, Michael Matz wrote:
> Hello,
>
> On Mon, 4 Jan 2021, Vincent Lefevre wrote:
>
> > > -
> > > #include
> > > #include
> > > #include
> > >
> > > int main(int argc, char **argv)
> > > {
> > > double d = strtod("-nan", NULL);
> > > d
Help,
Can you help me to recover the commits and give advice to Danny
Milosavljevic
to use git correctly.
Thanks,
Herman
On 1/5/21 2:40 PM, Danny Milosavljevic wrote:
Hi,
On Tue, 5 Jan 2021 07:25:33 +0100
Herman ten Brugge wrote:
I fixed this one also. But the problem is that below
Hi,
On Tue, 5 Jan 2021 18:12:35 +
Ramsay Jones wrote:
> I just pushed a fix-up to the 'mob' branch to recover three
> commits which had been 'overwritten' somehow. (Danny, did
> you not see an error message when you tried to push?).
Thank you!
I've reconstructed what could have happened.
On 05/01/2021 18:48, Herman ten Brugge wrote:
> I reapplied the last 2 patches again.
Oops, sorry did I mess-up? (I had the repo.or.cz website open
and, just before pushing, checked that no new commits had come
in - I also git a 'git fetch origin' just seconds before the
push!).
Sorry for the
Oops. I should have said:
I reapplied the last 2 *missing* patches again.
Everything is fine now.
Thanks for the help.
Herman
On 1/5/21 8:00 PM, Ramsay Jones wrote:
On 05/01/2021 18:48, Herman ten Brugge wrote:
I reapplied the last 2 patches again.
Oops, sorry did I mess-up? (I had
Hi Herman, Danny,
I just pushed a fix-up to the 'mob' branch to recover three
commits which had been 'overwritten' somehow. (Danny, did
you not see an error message when you tried to push?).
ATB,
Ramsay Jones
___
Tinycc-devel mailing list
I reapplied the last 2 patches again.
Herman
On 1/5/21 7:35 PM, Danny Milosavljevic wrote:
Hi,
On Tue, 5 Jan 2021 18:12:35 +
Ramsay Jones wrote:
I just pushed a fix-up to the 'mob' branch to recover three
commits which had been 'overwritten' somehow. (Danny, did
you not see an
Some tests which cannot be automatically generated:
1.
__asm__(".a:\n\t"
"mov r0, #1\n\t"
"bne .a");
2.
__asm__("mov r0, #1\n\t"
"bne L0\n\t"
"L0:\n\t");
3.
__asm__("mov r1, #2\n\t"
".L0:\n\t"
"mov r0, #1\n\t"
"bne .L0");
So maybe we
Michael Matz wrote:
So the current "-0.0-x" expansion of unary '-' needs a change. It
turned out to be a bit uglier than I wished for, ...
Hm, yes, the more as on x87 using just 'fchs' could be so easy.
Anyway, I tried to make it look a bit less ugly:
Hello,
On Tue, 5 Jan 2021, Danny Milosavljevic wrote:
On Tue, 5 Jan 2021 18:12:35 +
Ramsay Jones wrote:
I just pushed a fix-up to the 'mob' branch to recover three
commits which had been 'overwritten' somehow. (Danny, did
you not see an error message when you tried to push?).
Thank
Hello,
On Tue, 5 Jan 2021, Danny Milosavljevic wrote:
Hi,
On Mon, 4 Jan 2021 05:05:40 +0100 (CET)
Michael Matz wrote:
Yeah, put it into tests/ I'd say.
Ok, I've added it as tests/arm-asm-testsuite.sh .
The x86 assembler also has a little
testfile in there that isn't used by default
Danny Milosavljevic wrote:
So I think what happened is that one time I force-pushed and overwrote the mob
branch with a command like the one above (sorry). It should have only affected
a tiny bit though since I rebase arm-asm on top of mob.
Do not use the -f option with push, please.
In
Hello,
On Tue, 5 Jan 2021, Danny Milosavljevic wrote:
Some tests which cannot be automatically generated:
1.
__asm__(".a:\n\t"
"mov r0, #1\n\t"
"bne .a");
2.
__asm__("mov r0, #1\n\t"
"bne L0\n\t"
"L0:\n\t");
3.
__asm__("mov r1, #2\n\t"
".L0:\n\t"
Herman ten Brugge via Tinycc-devel wrote:
I fixed this one also. But the problem is that below commits are gone.
This happended after te commit 'arm-asm: Implement branch to label
Hi Herman,
Would you consider to review the "text relocation for arm" commit,
eventually?
Such copy & paste
Hi to all, and *happy new year*.
AFAIK neither -NaN nor +NaN have sense (how to put a sign at a 'not a
number' ).
So, d=-d is a non-sense too.
For instance, in my own language NaN have no sign, but on the other hand
I use -Inf and +Inf :
? (/ -1 0)
-Inf.
? (/ 1 0)
+Inf.
? (* 0 (/ -1 0))
Hello,
On Wed, 6 Jan 2021 00:07:07 +0100 (CET)
Michael Matz wrote:
> > Hmm, how can I get the name of the tcc executable to use for tests from
> > inside the shell script? Do I just use ./tcc ?
>
> Probably easiest to pass $(TCC) to the shell script as an argument I
> guess. It needs -B
Hello,
On Wed, 6 Jan 2021, ian wrote:
Hi to all, and happy new year.
AFAIK neither -NaN nor +NaN have sense (how to put a sign at a 'not a
number' ).
To be precise, the sense isn't specified. Like for the payload of IEEE
NaNs you can give it any meaning you like, including none. But
Hello,
On Wed, 6 Jan 2021, Danny Milosavljevic wrote:
Hello,
On Wed, 6 Jan 2021 00:07:07 +0100 (CET)
Michael Matz wrote:
Hmm, how can I get the name of the tcc executable to use for tests from
inside the shell script? Do I just use ./tcc ?
Probably easiest to pass $(TCC) to the shell
19 matches
Mail list logo
