Tamar Christina writes:
>> -Original Message-
>> From: Wilco Dijkstra
>> Sent: Tuesday, January 14, 2025 5:30 PM
>> To: Richard Sandiford
>> Cc: Richard Earnshaw ; ktkac...@nvidia.com; GCC
>> Patches ; sch...@linux-m68k.org
>> Subject:
> -Original Message-
> From: Wilco Dijkstra
> Sent: Tuesday, January 14, 2025 5:30 PM
> To: Richard Sandiford
> Cc: Richard Earnshaw ; ktkac...@nvidia.com; GCC
> Patches ; sch...@linux-m68k.org
> Subject: Re: [PATCH] AArch64: Deprecate -mabi=ilp32
>
>
Hi Richard,
>> + if (TARGET_ILP32)
>> + warning (OPT_Wdeprecated, "%<-mabi=ilp32%> is deprecated.");
>
> There should be no "." at the end of the message.
Right, fixed in v2 below.
> Otherwise it looks good to me, although like Kyrill says, it'll also
> need a release note.
I've added one,
Wilco Dijkstra writes:
> ILP32 was originally intended to make porting to AArch64 easier. Support was
> never merged in the Linux kernel or GLIBC, so it has been unsupported for many
> years. There isn't a benefit in keeping unsupported features forever, so
> deprecate it now (and it could be re
> On 13 Jan 2025, at 18:51, Richard Sandiford wrote:
>
> Iain Sandoe writes:
>> Hi Folks,
>>
>>> On 10 Jan 2025, at 18:30, Wilco Dijkstra wrote:
>>>
>>> Hi Andrew,
>>>
Personally I would like this deprecated even for bare-metal. Yes the
iwatch ABI is an ILP32 ABI but I don't see
Hi all,
> In that case, I'm coming round to the idea of deprecating ILP32.
> I think it was already common ground that the GNU/Linux support is dead.
> watchOS would use Mach objects rather than ELF. As you say, it isn't
> clear how much of the current ILP32 support would be relevant for it.
> An
Iain Sandoe writes:
> Hi Folks,
>
>> On 10 Jan 2025, at 18:30, Wilco Dijkstra wrote:
>>
>> Hi Andrew,
>>
>>> Personally I would like this deprecated even for bare-metal. Yes the
>>> iwatch ABI is an ILP32 ABI but I don't see GCC implementing that any
>>> time soon and I suspect it would not be
Hi Folks,
> On 10 Jan 2025, at 18:30, Wilco Dijkstra wrote:
>
> Hi Andrew,
>
>> Personally I would like this deprecated even for bare-metal. Yes the
>> iwatch ABI is an ILP32 ABI but I don't see GCC implementing that any
>> time soon and I suspect it would not be hard to resurrect the code at
>
Hi Andrew,
> Personally I would like this deprecated even for bare-metal. Yes the
> iwatch ABI is an ILP32 ABI but I don't see GCC implementing that any
> time soon and I suspect it would not be hard to resurrect the code at
> that point.
My patch deprecates it in all cases currently. It will be
On Fri, Jan 10, 2025 at 6:06 AM Wilco Dijkstra wrote:
>
>
> ILP32 was originally intended to make porting to AArch64 easier. Support was
> never merged in the Linux kernel or GLIBC, so it has been unsupported for many
> years. There isn't a benefit in keeping unsupported features forever, so
> d
On Jan 10 2025, Wilco Dijkstra wrote:
> diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
> index
> 17fe2c64c1f85ad8db8b61f040aafe5f8212e488..6722ad5281541e499d5b3916179d9a4d1b39097f
> 100644
> --- a/gcc/doc/invoke.texi
> +++ b/gcc/doc/invoke.texi
> @@ -21472,6 +21472,8 @@ The default depen
Wilco Dijkstra writes:
> ILP32 was originally intended to make porting to AArch64 easier. Support was
> never merged in the Linux kernel or GLIBC, so it has been unsupported for many
> years. There isn't a benefit in keeping unsupported features forever, so
> deprecate it now (and it could be re
Hi Wilco,
> On 10 Jan 2025, at 15:05, Wilco Dijkstra wrote:
>
>
> ILP32 was originally intended to make porting to AArch64 easier. Support was
> never merged in the Linux kernel or GLIBC, so it has been unsupported for many
> years. There isn't a benefit in keeping unsupported features foreve
ILP32 was originally intended to make porting to AArch64 easier. Support was
never merged in the Linux kernel or GLIBC, so it has been unsupported for many
years. There isn't a benefit in keeping unsupported features forever, so
deprecate it now (and it could be removed in a future release).
Pa
14 matches
Mail list logo
