News for hackers. Stuff that matters.

A comment on Aliasing. Parent comment

Re:Aliasing by pklausler on Monday December 22, 2025 @09:21AM (#46354320)
How does this bug concern aliasing?
[ Parent | on HN ]
Re:Aliasing by Etheryte on Monday December 22, 2025 @11:11AM (#46355303)
It's literally in the description? Because of aliasing, a variable that should've been zero became four.
[ Parent | on HN ]
Re:Aliasing by pklausler on Monday December 22, 2025 @11:57AM (#46355892)
It wasn't a variable.
[ Parent | on HN ]
Re:Aliasing by Etheryte on Monday December 22, 2025 @01:29PM (#46357074)
It wasn't intended to be a variable, but it did become one. Its value varied, it's in the name.
[ Parent | on HN ]
Re:Aliasing by pklausler on Monday December 22, 2025 @04:53PM (#46359588)
But this is just Fortran's call-by-reference in action. It's not aliasing.
[ Parent | on HN ]
Re:Aliasing by mrspuratic on Monday December 22, 2025 @02:39PM (#46357984)
In old school FORTRAN (I only recall WATFOR/F77, my uni's computers were quite ancient) subroutine (aka "subprogram") parameters are call-by-reference. If you passed a literal constant it would be treated as a variable in order to be aliased/passed by reference. Due to "constant pooling", modifications to a variable that aliased a constant could then propagate throughout the rest of the program where that constant[sic] was used.

"Passing constants to a subprogram" https://www.ibiblio.org/pub/languages/fortran/ch1-8.html

[ Parent | on HN ]