Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build mingw-w64-crt with -march=i486? #165

Open
FunkyFr3sh opened this issue Aug 27, 2024 · 2 comments
Open

build mingw-w64-crt with -march=i486? #165

FunkyFr3sh opened this issue Aug 27, 2024 · 2 comments

Comments

@FunkyFr3sh
Copy link

Do we really need crt1.o/crt1u.o/crt2.o/crt2u.o/dllcrt1.o/dllcrt2.o to be built with the default -march=pentium4? There shouldn't be anything performance-critical in there, or am I wrong?

Using -nostartfiles and -nostdlib could be used as a workaround, but it would be nice to be able to target -march=i486 without those switches as well.

@skeeto
Copy link
Owner

skeeto commented Aug 27, 2024 via email

@FunkyFr3sh
Copy link
Author

FunkyFr3sh commented Aug 27, 2024

Yeah I was only referring to C code, I think crt1.o/crt1u.o/crt2.o/crt2u.o/dllcrt1.o/dllcrt2.o are the only objects linked in that case. I wouldn't want libgcc without SSE either, I know it's huge improvement in performance.

I do have a custom build already with only crt1.o/crt1u.o/crt2.o/crt2u.o/dllcrt1.o/dllcrt2.o built with -march=i486, and everything else on default (-march=pentium4). I thought I suggest it here since it's kinda useful in some cases and doesn'T seem to have a real disadvantage.

Edit:
Only this here with "-march=i486" - Everything else stays on default
https://github.com/skeeto/w64devkit/blob/master/Dockerfile#L236

Repository owner deleted a comment from GoldenCaterpie Aug 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@skeeto @FunkyFr3sh and others