similar to: LLD default page size for arm32

The following patches shave some rough edges off the tools build system to allow cross compiling for at least arm32 and arm64 based on the Debian/Ubuntu multiarch infrastructure. They also add the necessary fixes to build for arm64 (which I have only tried cross, not native). I have posted some instructions on how to compile with these patches on the wiki:

So I'm playing around with S3 and elasticdrive, and I create a filesystem on it with a block size larger then 4k. mkfs.xfs -b size=8k /mnt/ed5/ed0 -f This completes fine and sets up the proper filesystem. When I try to mount it, however, I get: mount /mnt/ed5/ed0 /mnt/eds35/ -o loop mount: Function not implemented looking at dmesg I get: XFS: Attempted to mount file system with

Hi Ian, I am trying to add supporting dumping 32-bit guest on arm32 to see what happened in my dom0 kernel when booting. It seems gvirt_to_maddr() is not workable under arm32. But why has it been implemented both in include/asm-arm/arm{32,64}/page.h? Thanks. Baozi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel

Sorry, I initially included LLVM-Commits rather than LLVM-Dev. Fixed. On 26 January 2017 at 03:26, Serge Rogatch <serge.rogatch at gmail.com> wrote: > Hi Dean, Renato, > > AFAIK, unfortunately, these critical Arm32 XRay fixes are not yet in 4.0: > https://reviews.llvm.org/D28624 , https://reviews.llvm.org/D28623 . The > first repairs XRay instrumentation map emission.

https://bugs.freedesktop.org/show_bug.cgi?id=94757 Bug ID: 94757 Summary: powerpc64 & 64Kb kernel pagesize not working with nouveau Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

With all the talk about using lld on the list, I thought it would be interesting to try using it in my clang based ELLCC cross compilation tool chain. http://ellcc.org The change was simple, since I use configuration files to tell clang how to compile, where to find libraries, etc. I described the config files here: http://ellcc.org/blog/?p=13246 All I had to do was change the linker

Jordan, I have sent the patch via Phabricator: https://reviews.llvm.org/D69188 Let me know if I got it right. -- Tobias On Thu, Oct 17, 2019 at 7:12 PM Jordan Rupprecht <rupprecht at google.com> wrote: > > Tobias, > I don't have much experience with ARM, but from your report and Peter's explanation of why LLD does it, I agree we should be consistent with LLD and keep the

How is XRay tested? IIRC, Renato didn't see any test failures on ARM? Merging sounds reasonbaly, I'd just like to understand what's the risk for the branch. On Thu, Jan 26, 2017 at 10:29 AM, Serge Rogatch <serge.rogatch at gmail.com> wrote: > Hans, these changes reached trunk in https://reviews.llvm.org/rL292516 and > https://reviews.llvm.org/rL292517 . Could you look?

Hello Tobias, I think that looks reasonable to me, I think it will be down to the llvm-objcopy team whether they want to make .ARM.attributes a special case or not. The best way to find out is to submit a patch, citing the problems with old versions of libc, I'd expect that you'll need to add a test case for the patch to be accepted. To do that it is probably best to look at the existing

I'm wondering why the lit tests didn't catch this as part of testing rc1 on ARM. On Thu, Jan 26, 2017 at 11:25 AM, Serge Rogatch <serge.rogatch at gmail.com> wrote: > XRay is tested automatically on build-bots with tests in LLVM and > compiler-rt . Or are you asking for manual testing instructions? > Of these 2 patches, the compiler-rt patch depends on LLVM patch because

Hello Rui, Thanks for your reply. I tried with the keep-section argument and that made the shared library work. Should these sections be kept around by default maybe? -- Tobias On Thu, Oct 17, 2019 at 11:06 AM Rui Ueyama <ruiu at google.com> wrote: > > One thing I noticed is that llvm-strip seemed to remove a .ARM.attributes section. Can you try --keep-section=.ARM.attributes to

Hello, This is the second version of this patch series. I only implement the VPF context switch support for arm32 and add dummy function to avoid compilation on arm64. I have switched the order of the patch because the old second one can be applied alone and the patch are cleaner :). For all the changes see each patch. Cheers, Julien Grall (2): xen/arm: don''t enable VFP on XEN

Hi Rui, We meet a problem when enable the execute in place (XIP, https://en.wikipedia.org/wiki/Execute_in_place) for uefi firmware with lld-link. We need to set the COFF executable file SectionAlignment through the lld-link /ALIGN option, but we find the SectionAlignment is hardcoded to 4096 which cause the /ALIGN option doesn't work at all. Below is the hardcode in lld: lld\COFF\Writer.h

On 28 October 2016 at 23:02, Rui Ueyama via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Awesome results! I'm surprised! LLD is barely working on ARM at the moment. :) > I wonder if ARM32 BE is a real thing. I know that the processor is > bi-endian, but is there any system that uses ARM32 in big-endian mode? Yes... it is "a thing". :) ARM has two modes: BE32 and

I see. Thanks for clarifying. I'm Ok with merging these if Dean agrees, as I believe he's the code owner. Thanks, Hans On Thu, Jan 26, 2017 at 11:47 AM, Serge Rogatch <serge.rogatch at gmail.com> wrote: > There were no LLVM tests for presence of XRay instrumentation map in the > emitted assembly. You can see that https://reviews.llvm.org/D28624 adds this > check to the

On Fri, Oct 28, 2016 at 2:56 PM, Richard Pennington via cfe-dev < cfe-dev at lists.llvm.org> wrote: > With all the talk about using lld on the list, I thought it would be > interesting to try using it in my clang based ELLCC cross compilation tool > chain. http://ellcc.org > > The change was simple, since I use configuration files to tell clang how > to compile, where to

I am pleased to announce that LLVM 10 is now available. Get it here: https://llvm.org/releases/download.html#10.0.0 This release is the result of the LLVM community's work over the past six months (up to to e26a78e7085 on master plus commits up to d32170dbd5b on the release/10.x branch). Some highlights include: - C++ Concepts support in Clang - Clang no longer runs in a separate process

I am pleased to announce that LLVM 10 is now available. Get it here: https://llvm.org/releases/download.html#10.0.0 This release is the result of the LLVM community's work over the past six months (up to to e26a78e7085 on master plus commits up to d32170dbd5b on the release/10.x branch). Some highlights include: - C++ Concepts support in Clang - Clang no longer runs in a separate process

Ok, thanks! I got it going that way. I'd still love to hear from anyone off list working on similar stuff. ~Scott On Sun, Apr 30, 2017, at 03:32 PM, Joerg Sonnenberger wrote: > On Sun, Apr 30, 2017 at 03:18:35PM -0700, Scott Shawcroft via llvm-dev > wrote: > > Hi all, > > I've been doing a ton of embedded work (bare metal ARM Cortex M0+ and > > M4, hopefully RISCV

You can use these flags as described in the manual page to optimize access patterns, and to get better behaviour with the page cache in some scenarios. For my testing I used the cachedel and cachestats utilities written by Julius Plenz (https://github.com/Feh/nocache). I started with a 32 GB file of random data on a machine with about 32 GB of RAM. At the beginning of the test I evicted the