[Bug fortran/44856] Usage of array PARAMETERs: Literal copy vs. global variable

2015-11-09 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44856 Dominique d'Humieres changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|

[Bug fortran/44856] Usage of array PARAMETERs: Literal copy vs. global variable

2010-12-08 Thread burnus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44856 --- Comment #3 from Tobias Burnus 2010-12-08 16:28:07 UTC --- Other example - from James, cf. http://groups.google.com/group/comp.lang.fortran/browse_thread/thread/1a695db0fcfaa3e9 program kindtest use ISO_FORTRAN_ENV implicit none inte

[Bug fortran/44856] Usage of array PARAMETERs: Literal copy vs. global variable

2010-07-07 Thread burnus at gcc dot gnu dot org
--- Comment #2 from burnus at gcc dot gnu dot org 2010-07-07 15:23 --- Note: The tricky part for a simple fix is: moduleArray(i) If one simply wraps in resolve_code the code->expr(1,2) with parentheses (e = gfc_get_parentheses (e)") this leads to "D.123 = modulearray[i]", which does

[Bug fortran/44856] Usage of array PARAMETERs: Literal copy vs. global variable

2010-07-07 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2010-07-07 14:47 --- My idea is: a) For scalar expressions, generate simply always the scalar variable. b) For array accesses, generate a const variable at the beginning of the current block (subroutine, function, BLOCK) - if the variab