On 10/25/23 02:38, Thomas Schwinge wrote:
Hi!
Ping.
Grüße
Thomas
On 2023-09-19T10:47:56+0200, I wrote:
Hi!
Ping.
Grüße
Thomas
On 2023-09-08T14:02:50+0200, I wrote:
Hi!
On 2017-08-10T15:42:13+0200, Jan Hubicka <hubi...@ucw.cz> wrote:
On 07/31/2017 11:57 AM, Yuri Gribov wrote:
On Mon, Jul 31, 2017 at 9:04 AM, Martin Liška <mli...@suse.cz> wrote:
Doing the transformation suggested by Honza.
... which was:
| On 2017-07-24T16:06:22+0200, Jan Hubicka <hubi...@ucw.cz> wrote:
| > we probably should turn ASM_OUTPUT_DEF ifdefs into a conditional compilation
| > incrementally.
>From 78ee08b25d22125cb1fa248bac98ef1e84504761 Mon Sep 17 00:00:00 2001
From: marxin <mli...@suse.cz>
Date: Tue, 25 Jul 2017 13:11:28 +0200
Subject: [PATCH] Introduce TARGET_SUPPORTS_ALIASES
..., and got pushed as commit a8b522b483ebb8c972ecfde8779a7a6ec16aecd6
(Subversion r251048) "Introduce TARGET_SUPPORTS_ALIASES".
I don't know if that was actually intentional here, or just an
"accident", but such changes actually allow that a back end may or may
not provide symbol aliasing support ('TARGET_SUPPORTS_ALIASES')
independent of '#ifdef ASM_OUTPUT_DEF', and in particular, depending not
just on static but instead on dynamic (run-time) configuration. This is
relevant for the nvptx back end's '-malias' flag.
There did remain a few instances where we currently still assume that
from '#ifdef ASM_OUTPUT_DEF' follows 'TARGET_SUPPORTS_ALIASES', which I'm
adjusting in the attached (with '--ignore-space-change', for easy review)
"More '#ifdef ASM_OUTPUT_DEF' -> 'if (TARGET_SUPPORTS_ALIASES)' etc.".
OK to push?
These changes are necessary to cure nvptx regressions raised in
<https://inbox.sourceware.org/87iliurqt1....@euler.schwinge.homeip.net>
"[nvptx] Use .alias directive for mptx >= 6.3", addressing the comment:
"[...] remains to be analyzed".
OK
jeff
