search for: pext

I have a group of students working with me on some LLVM projects related to our Parabix research. One interesting issue that has come up for us is code generation support for the Haswell new instructions pext and pdep. These instructions shuffle bits within a 64-bit word, either gathering all selected bits to the beginning (pext) or scattering some initial bits throughout (pdep). A natural model for this is to use shufflevector on v32i1 and v64i1 vectors. We've got some preliminary notes here:...

...) { // Copy PCM data into ALBuffer alBufferData (id, eFormat, data, size, freq); ALErrorCheck (); } bool Buffer::Load (char *szFile, char *szErr) { ALint error; ALsizei size,freq; ALvoid *data; ALboolean loop; if (!szFile) return false; char *pExt = strstr (szFile, ".ogg"); if (pExt) { m_pOggStream = new OggStream; m_pOggStream->Load (szFile, szErr); m_eFormat = m_pOggStream->GetFormat (); } else { // assume is a wav file alutLoadWAVFile (szFile, &m_eFormat, &data, &siz...

Thanks for writing this up. I'd like to have this intrinsic too. Another argument for having the intrinsic is shown in PR37426: https://bugs.llvm.org/show_bug.cgi?id=37426 Vectorization goes overboard because the throughput cost model used by the vectorizers doesn't match the 6 IR instructions that correspond to 1 x86 rotate instruction. Instead, we have: $ opt 37426prevectorize.ll -S

Hi everyone! I recently ran into some interesting issues with generation of rotate instructions - the details are in the bug tracker (https://bugs.llvm.org/show_bug.cgi?id=37387 and related bugs) for those interested - and it brought up the issue of rotates in the IR again. Now this is a proposal that has been made (and been rejected) several times, but I've been told that this time round we