search for: 8gq18m

...pper <craig.topper at gmail.com>: > The i8 type in the pointers doesn't matter a whole lot. There's a long > term plan to remove the type from all pointers in llvm IR. > > Yes, clang will use memcpy for struct copies. You can see example IR here > https://godbolt.org/g/8gQ18m. You'll see that the struct pointers are > bitcasted to i8* before the call. > > ~Craig > > On Mon, Jan 29, 2018 at 11:12 PM, ma jun via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> >> Hi all >> I'm new here, and I have some question...

The i8 type in the pointers doesn't matter a whole lot. There's a long term plan to remove the type from all pointers in llvm IR. Yes, clang will use memcpy for struct copies. You can see example IR here https://godbolt.org/g/8gQ18m. You'll see that the struct pointers are bitcasted to i8* before the call. ~Craig On Mon, Jan 29, 2018 at 11:12 PM, ma jun via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > Hi all > I'm new here, and I have some question about llvm.memcpy intrinsic. > why...

...>>> The i8 type in the pointers doesn't matter a whole lot. There's a long >>> term plan to remove the type from all pointers in llvm IR. >>> >>> Yes, clang will use memcpy for struct copies. You can see example IR >>> here https://godbolt.org/g/8gQ18m. You'll see that the struct pointers >>> are bitcasted to i8* before the call. >>> >>> ~Craig >>> >>> On Mon, Jan 29, 2018 at 11:12 PM, ma jun via llvm-dev < >>> llvm-dev at lists.llvm.org> wrote: >>> >>>> >>...

Hi all I'm new here, and I have some question about llvm.memcpy intrinsic. why does llvm.memcpy intrinsic only support i8* for first two arguments? and does clang will also transform struct copy into llvm.memcpy ? what format does IR looks like? Thanks ! Regards Jun -------------- next part -------------- An HTML attachment was scrubbed... URL:

...gmail.com>: > >> The i8 type in the pointers doesn't matter a whole lot. There's a long >> term plan to remove the type from all pointers in llvm IR. >> >> Yes, clang will use memcpy for struct copies. You can see example IR here >> https://godbolt.org/g/8gQ18m. You'll see that the struct pointers are >> bitcasted to i8* before the call. >> >> ~Craig >> >> On Mon, Jan 29, 2018 at 11:12 PM, ma jun via llvm-dev < >> llvm-dev at lists.llvm.org> wrote: >> >>> >>> Hi all >>> I&...

...e i8 type in the pointers doesn't matter a whole lot. There's a long >>>> term plan to remove the type from all pointers in llvm IR. >>>> >>>> Yes, clang will use memcpy for struct copies. You can see example IR >>>> here https://godbolt.org/g/8gQ18m. You'll see that the struct pointers >>>> are bitcasted to i8* before the call. >>>> >>>> ~Craig >>>> >>>> On Mon, Jan 29, 2018 at 11:12 PM, ma jun via llvm-dev < >>>> llvm-dev at lists.llvm.org> wrote: >>>&g...

...pointers doesn't matter a whole lot. There's a long >>>>> term plan to remove the type from all pointers in llvm IR. >>>>> >>>>> Yes, clang will use memcpy for struct copies. You can see example IR >>>>> here https://godbolt.org/g/8gQ18m. You'll see that the struct >>>>> pointers are bitcasted to i8* before the call. >>>>> >>>>> ~Craig >>>>> >>>>> On Mon, Jan 29, 2018 at 11:12 PM, ma jun via llvm-dev < >>>>> llvm-dev at lists.llvm.org&g...