Bug 69815 - Don't always use BLOCKS for front-end optimization variables
Summary: Don't always use BLOCKS for front-end optimization variables
Status: NEW
Alias: None
Product: gcc
Classification: Unclassified
Component: fortran (show other bugs)
Version: 6.0
: P3 enhancement
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on: 82568
Blocks: 36854
  Show dependency tree / graph
 
Reported: 2016-02-14 13:20 UTC by Thomas Koenig
Modified: 2019-09-18 17:43 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed: 2016-02-16 00:00:00

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Koenig 2016-02-14 13:20:16 UTC 
Currently, when the front-end optimization passes creates a temporary variable,
this is put into a BLOCK.

This has led to some ICEs, most of which were resolved by simply not
doing the optimization in question.

However, it would be better to put the variable into the
main namespace if this is possible for such cases, if possible.
Comment 1 Dominique d'Humieres 2016-02-16 13:06:31 UTC 
> Currently, when the front-end optimization passes creates a temporary
> variable, this is put into a BLOCK.

What was the rationale for this choice?

> This has led to some ICEs, most of which were resolved by simply not
> doing the optimization in question.

Is there any open PR blocked by this one? If yes, could you please mark them as blocked?

> However, it would be better to put the variable into the
> main namespace if this is possible for such cases, if possible.

Agreed.