On Mon, Feb 17, 2025 at 9:51 AM Hongtao Liu <crazy...@gmail.com> wrote: > > On Thu, Feb 13, 2025 at 4:08 PM Haochen Jiang <haochen.ji...@intel.com> wrote: > > > > Hi all, > > > > According to the previous feedback on our RFC for AVX10 option adjustment > > and discussion with LLVM, we finalized how we are going to handle that. > > > > The overall direction is to re-alias avx10.x alias to 512 bit and only > > using -mno-avx10.x to disable everything instead of the current confusing > > -mno-avx10.x-[256,512], leading to deprecating -mno-avx10.x-[256,512]. > > > > It is fine for AVX10.2 since it is just introduced. However, it will become > > tricky for AVX10.1 introduced in GCC 14. Thus, we will deprecate > > avx10.1 alias. For -mno- options, since we do not have avx10.1, having > > -mno-avx10.1 would become weird. We will keep both -mno-avx10.1-256 and > > -mno-avx10.1-512, while changing -mno-avx10.1-512 also disabling the whole > > AVX10.1 to align with future. > > > > For option re-design to follow the latter length to determine the AVX10 > > size, we choose not to change that since it will break the previous > > impression on -m options should enable everything after that. Also it > > will make options like -mavx10.2-512 -mavx10.4-256 losing its flexibilty > > on only enabling 512 bit on AVX10.1/2 but enabling 256 bit on AVX10.3/4. > > > > Upcoming are the two patches, the first patch will be backported to > > GCC 14. Ok for trunk? > Ok. Please also add documents to gcc15 changes. > > > > Thx, > > Haochen > > > > > > > -- > BR, > Hongtao
-- BR, Hongtao
