[llvm] [BOLT][WIP] Always treat function entry as code (PR #160161)

Maksim Panchenko via llvm-commits llvm-commits at lists.llvm.org
Fri Oct 3 12:54:38 PDT 2025


maksfb wrote:

> > @yavtuk do you have an example where we have data at the start of the function? I'd like to consider us treating such cases differently, i.e. shift the function entry point to an actual code location.
> 
> Now I found only couple commits which can be related to this
> 
> [yavtuk/openssl at 28b80f2](https://github.com/yavtuk/openssl/commit/28b80f26eed28cd0163e159663d870eafbb6804e)
> 
> ```
> .type	_armv8_sm4_probe,%function
> _armv8_sm4_probe:
> 	AARCH64_VALID_CALL_TARGET
> 	.long	0xcec08400	// sm4e	v0.4s, v0.4s
> 	ret
> .size	_armv8_sm4_probe,.-_armv8_sm4_probe
> ```
> 
> also you can take a look at this commit [yavtuk/openssl at e0be006](https://github.com/yavtuk/openssl/commit/e0be006268c39c57ae03b76c48bcf5558960781b)
> 
> I'll add more specific details if I find them

This one makes sense. Even though it's better be using `.inst` directive, it's still code.

https://github.com/llvm/llvm-project/pull/160161


More information about the llvm-commits mailing list