On Fri, Dec 13, 2024 at 2:00 AM grischka via Tinycc-devel <
tinycc-devel@nongnu.org> wrote:
> On 12.12.2024 21:37, Scott Graham wrote:
> > Hi,
>
>
> > But would it make sense to restore the behaviour for normal `tcc -run`
> uses?
>
> Sure it makes sense. Fixed now. (The logic still relies on 're
On 12.12.2024 21:37, Scott Graham wrote:
Hi,
On origin/mob, before
https://repo.or.cz/tinycc.git/commit/dd2e5f8b06bc6ada943291fa4c67c8397038310f
the exit code of a script executed with `tcc -run` was the return code of its
main(), which I found useful for getting return codes from scripts.
Aft
Hi,
On origin/mob, before
https://repo.or.cz/tinycc.git/commit/dd2e5f8b06bc6ada943291fa4c67c8397038310f
the exit code of a script executed with `tcc -run` was the return code of
its main(), which I found useful for getting return codes from scripts.
After, though, it's been forced to be always 1
Hi,
On origin/mob, before
https://repo.or.cz/tinycc.git/commit/dd2e5f8b06bc6ada943291fa4c67c8397038310f
the exit code of a script executed with `tcc -run` was the return code of
its main(), which I found useful for getting return codes from scripts.
After, though, it's been forced to be always 1
