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

-mllvm -enable-machine-outliner=always Causes Compilation Timeout #121317

Open
guoxin049 opened this issue Dec 30, 2024 · 2 comments
Open

-mllvm -enable-machine-outliner=always Causes Compilation Timeout #121317

guoxin049 opened this issue Dec 30, 2024 · 2 comments

Comments

@guoxin049
Copy link
Contributor

guoxin049 commented Dec 30, 2024

i have demo like this https://godbolt.org/z/8b14dasMo, that times out when I try to build with clang.

@hstk30-hw
Copy link
Contributor

Has warning:

<source>:30:1: warning: stack frame size (1099511627808) exceeds limit (4294967295) in 'bar' [-Wframe-larger-than]
   30 | bar (void)
      | ^
<source>:41:1: warning: stack frame size (1099511627808) exceeds limit (4294967295) in 'baz' [-Wframe-larger-than]
   41 | baz (long i)
      | ^

Make sure the code have the behavior which you expected.

@guoxin049
Copy link
Contributor Author

Has warning:

<source>:30:1: warning: stack frame size (1099511627808) exceeds limit (4294967295) in 'bar' [-Wframe-larger-than]
   30 | bar (void)
      | ^
<source>:41:1: warning: stack frame size (1099511627808) exceeds limit (4294967295) in 'baz' [-Wframe-larger-than]
   41 | baz (long i)
      | ^

Make sure the code have the behavior which you expected.

Yes, the compilation is normal after I clear the alarm. However, if you do not use the -mllvm -enable-machine-outliner=always option, even with these alerts, you can compile normally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants