https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113570

--- Comment #1 from Vineet Gupta <vineetg at gcc dot gnu.org> ---
This one is a headache as we don't know where the problem is. And that it takes
~7hr for a QEMU run to finish.

Good this is there is a comparison point as VLA build works fine.

(1). bloat-o-meter (from Linux kernel) to diff the VLS (nok) and VLA (ok)
builds.

  Function                                     old     new   delta
  init_                                       6722    6752     +30
  __huygens_mod_MOD_huygense                 17078   17990    +912
  __huygens_mod_MOD_huygensh                 14412   15614   +1202
  __huygens_mod_MOD_uin.isra                  2922    2944     +22
  __material_mod_MOD_mat_updatee              4228    4272     +44

  __mur_mod_MOD_mur_init                      9054    9162    +108
  __mur_mod_MOD_mur_storee                    2546    2446    -100
  __mur_mod_MOD_mur_updatee                  10124   10354    +230

  __pec_mod_MOD_pec_init                      8522    8046    -476

  __plane_source_mod_MOD_plane_source_init    6942    7072    +130

  __power_mod_MOD___copy_power_mod_Powertyp      14      26     +12
  __power_mod_MOD_power_dft                   1280    1156    -124
  __power_mod_MOD_power_init                  9830    9994    +164
  __power_mod_MOD_power_print                 2304    1556    -748

  __upml_mod_MOD_upml_allocate.isra          19384   19614    +230
  __upml_mod_MOD_upml_init                   25564   26178    +614
  __upml_mod_MOD_upml_set_eps_arrays.isra     5406    6356    +950
  __upml_mod_MOD_upml_updatee                32516   27130   -5386
  __upml_mod_MOD_upml_updatee_simple         36112   29612   -6500
  __upml_mod_MOD_upml_updateh                15962   15992     +30

  writeout_                                  10856   11002    +146

(2). Assuming the issue is one of those above (which may not be the true),
manually  rebuild, changing build flags to VLA, one module at a time, relink,
rerun qemu and compare output.

   - This resulted in power.fppized.f90 as the culprit

(3) Manually split up the power module into multiple files - one function at a
time and do the same exercise to identify the function.

Reply via email to