[Patch] PR fortran/92470 Fixes for CFI_address

Tobias Burnus tobias@codesourcery.com
Tue Nov 12 20:29:00 GMT 2019


Hi all,

On 11/12/19 3:42 PM, Tobias Burnus wrote:
> (2) CFI_establish: For allocatables, it is clear – base_addr == NULL. 
> For pointers, it is clear as well – it has to be '0' according to the 
> standard. But for CFI_attribute_other … I have now asked at 
> https://mailman.j3-fortran.org/pipermail/j3/2019-November/thread.html#11740 
>

While I still have problems to decipher the standard, regarding 
CFI_establish, Steve L wrote:

"In the C descriptor world, arrays start at zero as they do in C. The 
only way they can become non-zero is through argument association, 
allocation or pointer association as specified in 18.5.3p3. For 
non-pointer, not-allocatable objects (this means "other"), the lower 
bounds are supposed to be always zero."

Hence, I now also set it for CFI_attribute_other to 0 – and check it in 
a test case (most users there have NULL as base_addr, hence, only a 
single assert is in that file).

Build on x86-64_gnu-linux.
OK for the trunk and GCC-9?

Tobias

-------------- next part --------------
A non-text attachment was scrubbed...
Name: establish-fix.diff
Type: text/x-patch
Size: 1603 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20191112/048d72d1/attachment.bin>


More information about the Gcc-patches mailing list