-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
improve zig cc flag integration #4784
Copy link
Copy link
Closed
Labels
contributor friendlyThis issue is limited in scope and/or knowledge of Zig internals.This issue is limited in scope and/or knowledge of Zig internals.enhancementSolving this issue will likely involve adding new logic or components to the codebase.Solving this issue will likely involve adding new logic or components to the codebase.zig ccZig as a drop-in C compiler featureZig as a drop-in C compiler feature
Milestone
Metadata
Metadata
Assignees
Labels
contributor friendlyThis issue is limited in scope and/or knowledge of Zig internals.This issue is limited in scope and/or knowledge of Zig internals.enhancementSolving this issue will likely involve adding new logic or components to the codebase.Solving this issue will likely involve adding new logic or components to the codebase.zig ccZig as a drop-in C compiler featureZig as a drop-in C compiler feature
Type
Fields
Give feedbackNo fields configured for issues without a type.
Extracted from #4774; see #3089 for the original issue.
llvm target triple vs zig target triple; llvm -mcpu vs zig -mcpuzig cc: parse-targetand-mcpu/-march/-mtuneflags according to clang #4911-fprofile-arcs)undefined symbol: __divtf3nostdinc and how it relates to the native targetnot neededstack protector argsnot neededomit-frame-pointernot neededzig cc: integration with -m flags #4912-margs affect cpu flags and-march=native