public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
* [gcc r13-500] [Ada] Remove useless code related to current value propagation
@ 2022-05-16 8:45 Pierre-Marie de Rodat
0 siblings, 0 replies; only message in thread
From: Pierre-Marie de Rodat @ 2022-05-16 8:45 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:20652c7f22b86d3cd646ecc2227a670f81302509
commit r13-500-g20652c7f22b86d3cd646ecc2227a670f81302509
Author: Piotr Trojanek <trojanek@adacore.com>
Date: Wed Mar 16 14:22:42 2022 +0100
[Ada] Remove useless code related to current value propagation
The current value propagation applies only to assignable objects and
doesn't make sense for subprogram entities. This was a mistake
introduced when extending the current value propagation years ago.
Cleanup related to fixing interference between expansion of attribute
Loop_Entry and current value propagation.
gcc/ada/
* sem_attr.adb (Address_Checks): Remove call to
Kill_Current_Values for subprogram entities, because this
routine only does something for object entities.
Diff:
---
gcc/ada/sem_attr.adb | 1 -
1 file changed, 1 deletion(-)
diff --git a/gcc/ada/sem_attr.adb b/gcc/ada/sem_attr.adb
index 55da9ef73f2..b3965f3664e 100644
--- a/gcc/ada/sem_attr.adb
+++ b/gcc/ada/sem_attr.adb
@@ -504,7 +504,6 @@ package body Sem_Attr is
begin
if Is_Subprogram (Ent) then
Set_Address_Taken (Ent);
- Kill_Current_Values (Ent);
-- An Address attribute is accepted when generated by the
-- compiler for dispatching operation, and an error is
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-05-16 8:45 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-05-16 8:45 [gcc r13-500] [Ada] Remove useless code related to current value propagation Pierre-Marie de Rodat
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).