On 10/12/15 18:49, Bernd Schmidt wrote: > On 10/11/2015 05:16 PM, Chen Gang wrote: >> For some architectures (e.g. bfin), when this case occurs, they will use >> another instructions instead of frame pointer (e.g. LINK for bfin), so >> they can still generate correct output assembly code. > > What is "this case"? I don't think you have explained the problem you are > trying to solve. >
It is about Bug65804. I found it when building Linux bfin kernel, and the original old version gcc can build kernel successfully. But since the git commit "e52beba PR debug/54694", it will be failed: it intends to check failure during building time. But for bfin, it has LINK insn instead of, so it is still OK, and gcc should not report failure. >> 2015-10-11 Chen Gang <gang.chen.5...@gmail.com> >> >> gcc/ >> * config.in: Add HAVE_FP_INSTEAD_INSNS. >> * configure: Check HAVE_FP_INSTEAD_INSNS to set 0 or 1. > > And of course, that should not be a configure check. If at all, use a target > hook. > OK, thanks. If we really need to fix it, which target hook should I use? (or do we need a new target hook?) Thanks. -- Chen Gang (陈刚) Open, share, and attitude like air, water, and life which God blessed