[cfe-dev] LLVM Dev Meeting - Talk Proposal Deadline 9/30

[James Molloy]

Hi,

Would there be interest in a BoF discussion on the state of cross-compilation and interacting with the toolchain? I'm thinking a discussion on how best to improve the experience of using the Clang driver for a cross-compiled or specialised target.

Cheers,

James
________________________________________
From: cfe-dev-bounces at cs.uiuc.edu [cfe-dev-bounces at cs.uiuc.edu] On Behalf Of dawn at burble.org [dawn at burble.org]
Sent: 27 September 2011 21:15
To: Eric Christopher
Cc: clang-dev Developers
Subject: Re: [cfe-dev] LLVM Dev Meeting - Talk Proposal Deadline 9/30

I don't know of anyone who's actually started working on either
localization or a VFS API.  But I'll hold off on the BoFs unless
we see more interest for them here...

-Dawn

On Tue, Sep 27, 2011 at 12:48:13PM -0700, Eric Christopher wrote:
>
> On Sep 27, 2011, at 11:26 AM, dawn at burble.org wrote:
>
> > On Tue, Sep 27, 2011 at 10:58:31AM -0700, Eric Christopher wrote:
> >>
> >> On Sep 27, 2011, at 10:53 AM, dawn at burble.org wrote:
> >>
> >>> Is there sufficient interest out there for BOFs on either:
> >>>
> >>> * unicode/localization, or
> >>
> >> Probably some here.
> >>
> >>> * VFS (virtual file system)
> >>>
> >>
> >> Could you be more specific here?
> >
> > The existing buffering requires that code be written out before it
> > can be passed to clang.  We would like to be able to pass code to clang
> > directly from a memory mapped file (e.g. from an un-saved editor buffer).
> >
> > On July 19, 2010, Daniel Dunbar wrote a good description here
> > http://article.gmane.org/gmane.comp.compilers.clang.devel/9653/match=virtual+file+system+daniel+dunbar.
>
> Seems reasonable. I don't know that It needs to be BoF session if you're just working on it.
>
> -eric
_______________________________________________
cfe-dev mailing list
cfe-dev at cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev


-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.