[cfe-dev] Is it possible to select UnknownArch through command line in clang?

Nikola Smiljanic popizdeh at gmail.com
Mon Jun 2 18:32:19 PDT 2014


Your change seem reasonable to me but I have no say. I suggest you send
this to cfe-commits for official review process.

Nikola


On Tue, Jun 3, 2014 at 8:12 AM, Zvonimir Rakamaric <zvonimir at cs.utah.edu>
wrote:

> Hi guys,
>
> So I created two tiny patches for LLVM and clang that allow target
> triples of the form x86_64-unknown-smack to be used, which in turn
> disables various type coercions.
>
> I tested the patches on both LLVM and clang regressions suites, and
> they seem to be working fine.
>
> Please let me know how to proceed with this.
>
> Thanks!
>
> Best,
> -- Zvonimir
>
>
> --
> http://zvonimir.info
> http://soarlab.org/
>
>
> On Wed, May 28, 2014 at 12:28 PM, Zvonimir Rakamaric
> <zvonimir at cs.utah.edu> wrote:
> > On Wed, May 28, 2014 at 12:17 PM, Reid Kleckner <rnk at google.com> wrote:
> >> On Tue, May 27, 2014 at 7:56 PM, Zvonimir Rakamaric <
> zvonimir at cs.utah.edu>
> >> wrote:
> >>>
> >>> One final question: why does DefaultTargetCodeGenInfo even exist if it
> >>> cannot be selected?
> >>
> >> DefaultTargetCodeGenInfo is essentially an abstract base class for other
> >> ABIs.
> >>
> >> I think you should do something like what PNaCl does and add a new
> virtual
> >> ISA like "smack64" or "le64" that has a known data layout, endianness,
> etc,
> >> and always uses 'byval' when passing structs by value.
> >
> > This is a great suggestion, thanks!
> > Is there any chance that something like smack64 would be integrated
> > into the main trunk of clang?
> >
> > Since the main reason why I started this discussion was to hopefully
> > come up with a solution that would ultimately not require a patch to
> > clang to be applied whenever somebody would like to use it with SMACK.
> >
> > Thanks!
> > -- Zvonimir
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20140603/faa184e9/attachment.html>


More information about the cfe-dev mailing list