search for: aapcs_vfp

On 7/23/14, 3:30 PM, Tim Northover wrote: [...] > It looks like it's a case of calling Module::setTargetTriple. As with > most JIT setup questions, though, often the best way to find out is to > get something working in lli and then look at what it does > (tools/lli/lli.cpp). Well, it's *almost* working --- hardfloat code is now being generated, and it even seems to be right

...my triple doesn't apply? Should I be setting the triple on the execution engine as a whole (which I've avoided so far because the API looks painful)? [...] > Did you try setting a breakpoint in that function I mentioned and > finding out just which test fails on the path to returning AAPCS_VFP? No; I don't have a debugger on this platform. -- ┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ───── │ "Feminism encourages women to leave their husbands, kill their │ children, practice withcraft, destroy capitalism and become lesbians." │ --- Rev. Pat Robertson -------------...

Hi Sandeep, >> The ARM backend now supports struct byval for APCS. Extending it to support AAPCS shouldn't be too difficult. Alas, I won't have time to revisit this in the near future. > > It's slightly unclear to me what byval means for an ABI that passes > some structs in registers, such as AAPCS-VFP. I think in that case the front-end is supposed to extract the

On 29 Apr 2012, at 23:44, Bill Wendling wrote: > - Module-level flags would be used for those options which affect the whole module and which prevent two modules that do not have that flag set from being merged together. For example, `-msoft-float' changes the calling convention in the output file. Therefore, it's only useful if the whole program is compiled with it. It would be a

I have some needs in the Mips compiler to have some special calling conventions; for now just used internally by the compiler. In the ir there is the general "cc <n>". Is there a way to register a calling convention with target independent code so that if those attribute is attached to the function ir , that the corresponding calling convention will be used when generating

Hi, Link-Time Optimization has a problem. We need to preserve some of the flags with which the modules were compiled so that the semantics of the resulting program are correct. For example, a module compiled with `-msoft-float' should use library calls for floating point. And that's only the tip of the proverbial iceberg. Goals ===== My goals for whichever solution we come up with are