forked from OSchip/llvm-project
564d85e090
In LLVM IR, `AlignmentBitfieldElementT` is 5-bit wide But that means that the maximal alignment exponent is `(1<<5)-2`, which is `30`, not `29`. And indeed, alignment of `1073741824` roundtrips IR serialization-deserialization. While this doesn't seem all that important, this doubles the maximal supported alignment from 512MiB to 1GiB, and there's actually one noticeable use-case for that; On X86, the huge pages can have sizes of 2MiB and 1GiB (!). So while this doesn't add support for truly huge alignments, which i think we can easily-ish do if wanted, i think this adds zero-cost support for a not-trivially-dismissable case. I don't believe we need any upgrade infrastructure, and since we don't explicitly record the IR version, we don't need to bump one either. As @craig.topper speculates in D108661#2963519, this might be an artificial limit imposed by the original implementation of the `getAlignment()` functions. Differential Revision: https://reviews.llvm.org/D108661 |
||
|---|---|---|
| .. | ||
| dr0xx.cpp | ||
| dr1xx.cpp | ||
| dr2xx.cpp | ||
| dr3xx.cpp | ||
| dr4xx.cpp | ||
| dr5xx.cpp | ||
| dr6xx.cpp | ||
| dr7xx.cpp | ||
| dr9xx.cpp | ||
| dr10xx.cpp | ||
| dr11xx.cpp | ||
| dr12xx.cpp | ||
| dr13xx.cpp | ||
| dr14xx.cpp | ||
| dr15xx.cpp | ||
| dr16xx.cpp | ||
| dr17xx.cpp | ||
| dr18xx.cpp | ||
| dr19xx.cpp | ||
| dr20xx.cpp | ||
| dr21xx.cpp | ||
| dr22xx.cpp | ||
| dr23xx.cpp | ||
| dr118.cpp | ||
| dr158.cpp | ||
| dr412.cpp | ||
| dr1748.cpp | ||