On Fri, Oct 12, 2012 at 1:09 AM, jerro <[email protected]> wrote: > I've added a gen_gccbuiltins.cpp to my fork of LDC at > https://github.com/jerro/ldc/commit/3500f3489aaf9f95e9b5c469c438efc6845ec1ee > and modified the cmake scripts so that gccbuiltns.di is generated at built > time and installed in $prefix/include/d/ldc/ .
Nice, thanks a lot for your work! > Do you have an opinion on where gen_gccbuiltins.cpp should go? Do you think > this is the right way to add gccbuiltins.di ? If so, I will be making a pull > request. Yes, top-level is not optimal, it's way too crowded as it is. We should really have a src directory, but I don't want to break all the history and patches right now (but I'll probably move all the config files to a separate directory). What about just runtime/, or maybe better a new util/ directory? But yes, I think this is the right way to handle GCC intrinsics, so it would be great if you could prepare a pull request. One little note: It seems like you only generate the x86 intrinsics. I have not looked at the matter in detail – would it make sense to include the architecture in the module name so we can have multiple archs side by side (cross-compiling, ...)? The build system should probably also handle the case where host/target are not x86, but this can wait until a later point in time. David -- You received this message because you are subscribed to the Google Groups "LDC - the LLVM D compiler" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/ldc-dev?hl=en.
