search for: smeenai

I’m happy to run them, although I’d appreciate a pointer to the appropriate documentation. From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Tobias Hieta via llvm-dev <llvm-dev at lists.llvm.org> Reply-To: Tobias Hieta <tobias at plexapp.com> Date: Wednesday, September 30, 2020 at 11:15 AM To: Hans Wennborg <hans at chromium.org> Cc: llvm-dev <llvm-dev at

..., Mar 15, 2019, 12:20 PM Shoaib Meenai via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Ping. > > > > Would anyone be opposed to me trying to revive the in-tree Mach-O TAPI > code? > > > > Thanks, > > Shoaib > > > > *From: *Shoaib Meenai <smeenai at fb.com> > *Date: *Wednesday, March 6, 2019 at 9:22 PM > *To: *"llvm-dev at lists.llvm.org" <llvm-dev at lists.llvm.org> > *Cc: *"juergen at ributzka.de" <juergen at ributzka.de>, Hans Wennborg < > hans at chromium.org> > *Subject: *What'...

https://reviews.llvm.org/rL353906 introduced (presumably accidentally) the "b" top-level directory to the monorepo. The files should be moved to their proper location, but I'm also wondering if there's any way to prevent accidental top-level additions like this. Thanks, Shoaib -------------- next part -------------- An HTML attachment was scrubbed... URL:

...urs has actual response files, so my patch won't help there. CCing Reid and Hans, who did a bunch of the implementation in this area. From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Shoaib Meenai via llvm-dev <llvm-dev at lists.llvm.org> Reply-To: Shoaib Meenai <smeenai at fb.com> Date: Friday, April 26, 2019 at 8:34 AM To: Chris Glover <chrisglover at google.com>, "llvm-dev at lists.llvm.org" <llvm-dev at lists.llvm.org> Subject: Re: [llvm-dev] Total response file count limited to 21 Hi Chris, I fixed this in https://reviews.llvm.org/D6...

...unded to me from your original message that you have an urgent need to upgrade to 3.8. Were you planning on going ahead with that right away? From: llvm-dev <llvm-dev-bounces at lists.llvm.org> On Behalf Of Louis Dionne via llvm-dev Sent: Thursday, April 2, 2020 7:20 AM To: Shoaib Meenai <smeenai at fb.com> Cc: llvm-dev at lists.llvm.org Subject: [EXT] Re: [llvm-dev] Upgrading LLVM's minimum required CMake version Okay, so we've had some discussion on this thread, and although some people (including me) would like a more aggressive policy, I believe the following will not get an...

...er still requires funclet operand > bundles, it sounds like one of the 3 options below will be required until a > longer term project of eliminating them is available. Anybody have a strong > preference? > > Chris > > > -----Original Message----- > From: Shoaib Meenai <smeenai at fb.com> > Sent: Monday, January 13, 2020 1:10 AM > To: Chrulski, Christopher M <christopher.m.chrulski at intel.com>; > llvm-dev at lists.llvm.org > Cc: Reid Kleckner <rnk at google.com> > Subject: Re: [llvm-dev] Incorrect code generation when using > -fprofile-g...

...alf of Andrew Kelley via llvm-dev <llvm-dev at lists.llvm.org> Reply-To: Andrew Kelley <superjoe30 at gmail.com> Date: Sunday, June 4, 2017 at 1:15 PM To: LLVM Dev <llvm-dev at lists.llvm.org> Subject: Re: [llvm-dev] trying to get a minimal windows program linked with lld Update: smeenai from #llvm has been helping me with this, and we narrowed it down to kernel32.lib being no good. kernel32.lib from the 14393 SDK worked fine. My goal is to not depend on .lib files from the SDK, so there's still a problem to solve here. On Sun, Jun 4, 2017 at 3:33 PM, Andrew Kelley <super...

...// Symbol section+offset are evaluated here. It seems that github issues may be a good place to record the problem. I just created https://github.com/llvm/llvm-project/issues/52 I wanted to mark it low priority, but there is no such label. On Wed, Dec 4, 2019 at 8:51 AM Shoaib Meenai <smeenai at fb.com> wrote: > I completely agree that --defsym foo=bar should keep bar (or more > precisely the section containing bar) alive if foo is referenced. > > My mental model of how --defsym foo=bar behaves is that (assuming bar is a > defined symbol) we create a symbol foo that p...

If you want to use your key to authenticate, you need to set your remote URL to the SSH one: git remote set-url --push origin git at github.com:llvm/llvm-project.git You can get the SSH URL by going to https://github.com/llvm/llvm-project/ and clicking on Clone or download to get the appropriate URL ... it should give you the option to Clone with SSH. I've not had a ton of luck with HTTPS

As a frontend, what are the downsides of enabling --no-rosegment by default? So far the pro list is: * valgrind debug info will work by default What's on the con list? On Thu, Apr 5, 2018 at 5:16 PM, Shoaib Meenai <smeenai at fb.com> wrote: > It's more of a valgrind issue than an LLD issue, but you can work around > it by linking with --no-rosegment > > > > *From: *llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Andrew > Kelley via llvm-dev <llvm-dev at lists.llvm.org&...

> On Mar 3, 2020, at 17:16, Shoaib Meenai <smeenai at fb.com> wrote: > > `arc patch` should preserve the author information in the original commit, if there was any. At least it has in my experience. Yes, but I think people can upload raw patches to Phabricator without using `arc diff`. I know I ran into one of these just last week where...

Hi all, It looks like Juergen landed the TextAPI libraries for Mach-O in https://reviews.llvm.org/D53945, and also had several follow-ups, but then it was deleted entirely by r347874. I'm not sure if the entire deletion was intentional, since the commit message only mentions reverting a certain series of patches; CC Hans. In any case, I'm wondering if there are plans to revive it, since

....8.0 now and then upgrade to 3.13.4 after the branch, would people be okay with that, or should we limit upgrades to just shortly after a branch? From: <ldionne at apple.com> on behalf of Louis Dionne <ldionne at apple.com> Date: Thursday, April 2, 2020 at 7:20 AM To: Shoaib Meenai <smeenai at fb.com> Cc: "llvm-dev at lists.llvm.org" <llvm-dev at lists.llvm.org>, Chris Bieneman <beanz at apple.com>, Petr Hosek <phosek at chromium.org>, Saleem Abdulrasool <compnerd at compnerd.org>, "tstellar at redhat.com" <tstellar at redhat.com> S...

(switching list from llvm-commits to llvm-dev, which seems more appropriate here) From: llvm-commits <llvm-commits-bounces at lists.llvm.org> on behalf of Rui Ueyama via llvm-commits <llvm-commits at lists.llvm.org> Reply-To: Rui Ueyama <ruiu at google.com> Date: Friday, October 13, 2017 at 4:22 PM To: Rafael Avila de Espindola <rafael.espindola at gmail.com> Cc:

...t on your behalf. If you commit yourself, then whatever. Louis > > -eric > > On Tue, Mar 3, 2020 at 2:20 PM Louis Dionne via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > > > > On Mar 3, 2020, at 17:16, Shoaib Meenai <smeenai at fb.com <mailto:smeenai at fb.com>> wrote: > > > > `arc patch` should preserve the author information in the original commit, if there was any. At least it has in my experience. > > Yes, but I think people can upload raw patches to Phabricator without using `arc diff`...

...> As a frontend, what are the downsides of enabling --no-rosegment by >> default? >> >> So far the pro list is: >> * valgrind debug info will work by default >> >> What's on the con list? >> >> On Thu, Apr 5, 2018 at 5:16 PM, Shoaib Meenai <smeenai at fb.com> wrote: >> >>> It's more of a valgrind issue than an LLD issue, but you can work around >>> it by linking with --no-rosegment >>> >>> >>> >>> *From: *llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Andrew...

...r “MayStore.” > For loads, the scheduling model provides an “optimistic” load-to-use > latency (which usually matches the load-to-use latency for when there is a > hit in the L1D).” > > > > Hope that helps, > > -Matt > > > > > > *From: *Shoaib Meenai <smeenai at fb.com> > *Date: *Thursday, May 2, 2019 at 11:34 AM > *To: *lorenzo chelini <l.chelini at icloud.com>, "llvm-dev at lists.llvm.org" < > llvm-dev at lists.llvm.org>, Matt Davis <nullptr at fb.com> > *Subject: *Re: [llvm-dev] Llvm-mca library. > > &...

...rjoe30 at gmail.com> wrote: > As a frontend, what are the downsides of enabling --no-rosegment by > default? > > So far the pro list is: > * valgrind debug info will work by default > > What's on the con list? > > On Thu, Apr 5, 2018 at 5:16 PM, Shoaib Meenai <smeenai at fb.com> wrote: > >> It's more of a valgrind issue than an LLD issue, but you can work around >> it by linking with --no-rosegment >> >> >> >> *From: *llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Andrew >> Kelley via llvm-dev...

...okay with that, or should we limit upgrades to just shortly after a branch? From: <ldionne at apple.com<mailto:ldionne at apple.com>> on behalf of Louis Dionne <ldionne at apple.com<mailto:ldionne at apple.com>> Date: Thursday, April 2, 2020 at 7:20 AM To: Shoaib Meenai <smeenai at fb.com<mailto:smeenai at fb.com>> Cc: "llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>" <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>>, Chris Bieneman <beanz at apple.com<mailto:beanz at apple.com>>, Petr Hosek <p...

Hi all (CC llvm-rc contributors), I've been attempting to cross-compile LLVM for Windows using clang-cl. LLVM's build system embeds resource files for MSVC builds, so I was hoping to use llvm-rc for that portion. cmake invokes the resource compiler with arguments joined to their options (e.g. `/D_WIN32`, `/fofoo.res`, etc.), which rc.exe supports, but llvm-rc expects arguments to be