Re: [Tinycc-devel] It seem I pull code in wrong way. How can I revert it?

avih via Tinycc-devel wrote: While force-pushing is usually possible, I'd argue that at the tcc repo (and generally elsewhere too, but to each his own practices) no one should force push except maybe maintainers and maybe other regular contributors which 100% know what they're doing when force-p

Re: [Tinycc-devel] Request for "fix float to u64 intrinsics"

I sent this in a private mail to Kyryl but it probably should also be sent to the list. After 'add tests for float conversions to u64 ' I get the following output: x86_64 (linux + macos): ok x86_64 (windows), i38

[Tinycc-devel] mob in bad state?

The few last commits leave mob in bad state!! The last state on which I trust is after my revert “Revert commit 55f8963dfab5c543f7f34589d3ef9d3f2da3db14 from wanjochan until better tested on all platforms” After this one: Minor issue: Kyryl “add tests for float conversions to u64” added variable

Re: [Tinycc-devel] It seem I pull code in wrong way. How can I revert it?

While force-pushing is usually possible, I'd argue that at the tcc repo (and generally elsewhere too, but to each his own practices) no one should force push except maybe maintainers and maybe other regular contributors which 100% know what they're doing when force-pushing. I.e. if you want some

Re: [Tinycc-devel] It seem I pull code in wrong way. How can I revert it?

Hi! Force pushing is dangerous, make sure to have a copy of the repo backed up! Sometimes it's necessary though. If you need to do it, make sure that each developer re-clones the repository! I had to do it yesterday for https://github.com/opennars/opennars-for-applications as one author pushed wit

Re: [Tinycc-devel] It seem I pull code in wrong way. How can I revert it?

I found a way to remove these empty commit, by use "git rebase -i".  But I can't push these change without -f flag, and I have been told that do NOT use "git push -f". So I can only give up to revert it. -- Original -- From:

Re: [Tinycc-devel] Request for "fix float to u64 intrinsics"

On 2020-09-11 11:11:47 +, Kyryl Melekhin wrote: > If this is undefined behavior, then this line is straight up also UB. > https://repo.or.cz/tinycc.git/blobdiff/55f8963dfab5c543f7f34589d3ef9d3f2da3db14..310e3b428cfd181b51723276e6563b90d670da06:/tccgen.c > And because that line is UB, then it ca

Re: [Tinycc-devel] It seem I pull code in wrong way. How can I revert it?

Pursuer - On Fri, Sep 11, 2020 at 11:27:05PM +0800, Pursuer wrote: > I'm sorry that I pull code in wrong way.  > And now there are many commit like  > Merge branch 'mob' of git://repo.or.cz/tinycc into mob > How can I remove them. Obligatory xkcd: https://xkcd.com/1597/ There are fancier (

[Tinycc-devel] It seem I pull code in wrong way. How can I revert it?

I'm sorry that I pull code in wrong way.  And now there are many commit like  Merge branch 'mob' of git://repo.or.cz/tinycc into mob How can I remove them.___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/l

Re: [Tinycc-devel] Request for "fix float to u64 intrinsics"

If this is undefined behavior, then this line is straight up also UB. https://repo.or.cz/tinycc.git/blobdiff/55f8963dfab5c543f7f34589d3ef9d3f2da3db14..310e3b428cfd181b51723276e6563b90d670da06:/tccgen.c And because that line is UB, then it causes even more bugs down the drain. At least if the output

Re: [Tinycc-devel] Request for "fix float to u64 intrinsics"

On 2020-09-11 10:32:06 +, Kyryl Melekhin wrote: > I guess I'll explain the bug here as well. > consider this code: > > float a = -123.987; > printf("%lu", (unsigned long int)a); > > Before the patch output would be 123. > After the patch output would be 18446744073709551493. There's no bug.

Re: [Tinycc-devel] Request for "fix float to u64 intrinsics"

Hi Christian, I completely understand what you mean about potential regressions. If that is the case it would be trivial to wrap the code into #ifdef. By the way you mentioned Aarch64 long double precision, well that will not be a problem because if you look at existing source code, function __fix