[all-commits] [llvm/llvm-project] 8dc659: [Hexagon] Add an explicit makeArrayRef to pacify g...

[topperc via All-commits]

  Branch: refs/heads/master
  Home:   https://github.com/llvm/llvm-project
  Commit: 8dc659c131f830911e9dd0c83f3b7a884c027739
      https://github.com/llvm/llvm-project/commit/8dc659c131f830911e9dd0c83f3b7a884c027739
  Author: Craig Topper <craig.topper at intel.com>
  Date:   2020-02-14 (Fri, 14 Feb 2020)

  Changed paths:
    M llvm/lib/Target/Hexagon/MCTargetDesc/HexagonMCTargetDesc.cpp

  Log Message:
  -----------
  [Hexagon] Add an explicit makeArrayRef to pacify gcc 5.5

The array seemed to have decayed to a pointer before the ArrayRef
constructor got called so there was no size information available.


  Commit: 1fe6e6fd85f7da3b216fbb189ce365303512ad35
      https://github.com/llvm/llvm-project/commit/1fe6e6fd85f7da3b216fbb189ce365303512ad35
  Author: Craig Topper <craig.topper at intel.com>
  Date:   2020-02-14 (Fri, 14 Feb 2020)

  Changed paths:
    M llvm/tools/llvm-exegesis/lib/SnippetGenerator.h

  Log Message:
  -----------
  [llvm-exegesis] Rename range based for loop variable in a unit test so its different than the container being iterated over. NFC

It seems like gcc 5.5 wants to iterate over the new variable instead
of the container that lives outside the loop. But of course this
new container is empty.

Plus using a different variable names makes the code more readable.


Compare: https://github.com/llvm/llvm-project/compare/d7058acc145c...1fe6e6fd85f7