Re: [gccsdk] Absolute binaries giving incorrect __riscosify_control

2018-04-22 Thread Duncan Moore
On 20/04/2018 17:00, Lee Noar wrote: On 19/04/18 12:51, Theo Markettos wrote: On Wed, Apr 18, 2018 at 01:44:45PM +0100, Duncan Moore wrote: I have ELF and Absolute binaries getting different values of __riscosify_control from UnixEnv$progname$nonametrans. It's the Absolute binary that is

Re: [gccsdk] Absolute binaries giving incorrect __riscosify_control

2018-04-20 Thread Lee Noar
On 19/04/18 12:51, Theo Markettos wrote: On Wed, Apr 18, 2018 at 01:44:45PM +0100, Duncan Moore wrote: This is a bug report, but since the bug reporting list has been out of action for some time, I'm sending it here. Thanks. We should probably start a new issue tracker on github and migrate

Re: [gccsdk] Absolute binaries giving incorrect __riscosify_control

2018-04-19 Thread Theo Markettos
On Wed, Apr 18, 2018 at 01:44:45PM +0100, Duncan Moore wrote: > This is a bug report, but since the bug reporting list has been out of > action for some time, I'm sending it here. Thanks. We should probably start a new issue tracker on github and migrate across. (apologies for closing some of