search for: driverargs

...You passed `-target -i386`, >which is a triple with no OS, so Clang is doing something arbitrary. Grepping >Clang sources shows that this flag is handled in an OS-specific manner: > >$ git grep -i fuse_init_array ../clang/lib/Driver/ >../clang/lib/Driver/ToolChains/Fuchsia.cpp:  if (DriverArgs.hasFlag >(options::OPT_fuse_init_array, >../clang/lib/Driver/ToolChains/Gnu.cpp:  if (DriverArgs.hasFlag >(options::OPT_fuse_init_array, >../clang/lib/Driver/ToolChains/NetBSD.cpp:  if (DriverArgs.hasFlag >(options::OPT_fuse_init_array, >../clang/lib/Driver/ToolChains/WebAssembly....

Hi Devs, consider below testcases, $cat test.cc class B { public: B(int t) { j=t; } int j; }; B b(1); ============== $clang test.cc -target -i386 -c -fuse-init-array $llvm-objdump -h test.o |grep ctors 7 .ctors 00000004 00000000 DATA 8 .rel.ctors 00000008 00000000 As you can see it ignores the -fuse-init-array options.It happens for x86,Other target like aarch64 is doing fine.

Makes sense, yeah, trying something in a different environment is usually a good way to find problems. I had indeed moved the renamed clang-cl.exe to a different directory, but when I move it back into its home directory and retry the build, I get the same errors. On Thu, Jun 11, 2015 at 11:16 PM, Reid Kleckner <rnk at google.com> wrote: > Thanks for trying the self-host, it's

Hi, We are now about halfway between the 3.4 and 3.5 releases, and I would like to start preparing for a 3.4.1 release. Here is my proposed release schedule: Mar 26 - April 9: Identify and backport additional bug fixes to the 3.4 branch. April 9 - April 18: Testing Phase April 18: 3.4.1 Release How you can help: - If you have any bug fixes you think should be included to 3.4.1, send me an