search for: abiname

Hi folks Some proposed changes: * Fixiate the API/ABI of some libs, for the stable version, including - libxenctrl, - libxenstat, - libxenstore. As upstream don't know what abinames are for, roll own abinames. * Add libxenctrlX, libxenstatX, libxenstoreX, if abinames may be different or libxenX if the abinames should the same for all libs. * Add libxen-dev including - static libxenctrl, libxenstat, libxenstore, - maybe static libxenapi, - public Xen headers, - libra...

...ding on what's necessary That's correct and r224492 is quite similar to what I'm trying to do in this patch series (see below). I should mention that even that commit relies on the ABI being encoded in the triple though. In computeTargetABI() from ARMTargetMachine.cpp, MCTargetOptions::ABIName specifies the ABI if it is a non-empty string but the code otherwise falls back on extracting the ABI from the triple. The clang driver has similar code, it determines the value for the –target-abi option from –mabi if it's given and falls back on calculating it from the triple using the same c...

...ing what happens to Triple::GNU for triples like mips-linux-gnu and mips64-linux-gnu. The answer to this is that the API-user (e.g. clang) is expected to normalize such triples down to one of Triple::GNUABI32/GNUABIN32/GNUABI64. This can be as simple as adding: Triple ABITriple = TT.getABIVariant(ABIName); // ABIName can be the empty string to get the default ABI. if (ABITriple.getArch() != Triple::UnknownArch) { TT = ABITriple; ABIName = ""; // <- Only needed if this would end up in MCTargetOptions::ABIName. } to the appropriate place in the caller. This is the same way cl...

...f tools-libxc-prefix.diff tools-misc-prefix.diff @@ -18,6 +19,7 @@ tools-xentrace-prefix.diff tools-rpath.diff tools-blktap-rpath.diff tools-console-rpath.diff +tools-ioemu-rpath.diff tools-libfsimage-rpath.diff tools-libxc-rpath.diff tools-misc-rpath.diff @@ -35,8 +37,7 @@ tools-libfsimage-abiname.diff tools-libxc-abiname.diff tools-python-xen-xm-relative-path.diff +tools-ioemu-config.diff tools-misc-xend-startup.diff -config-ioemu-disable.diff - tools-blktap-crypto.patch --- /dev/null +++ xen-3/debian/patches/tools-ioemu-config.diff @@ -0,0 +1,13 @@ +--- tools/ioemu-qemu-xen/xen-con...

On 23 May 2015 at 00:08, Jim Grosbach <grosbach at apple.com> wrote: > This is the key question. The LLVM assumption is that these sorts of things > are inferable from the triple. Your observation here that the GNU world’s > notion of triples and LLVM’s need not be the same is a good one. Having a > split and a translation up in clang seems an interesting avenue to explore. >

...00000 -0600 @@ -70,3 +70,31 @@ setup-i386-i386-pae-real: $(MAKE) -f debian/rules.real setup-flavour MAJOR='3.0' FLAVOUR='i386-pae' CONFIG='pae=y' SUBARCH='none' SHORT_VERSION='3.0' EXTRAVERSION='.4' VERSION='3.0.4' XEN_ARCH='x86_32' ABINAME='-1' ARCH='i386' source-i386-i386-pae-real: +binary-arch:: binary-arch-ia64 +binary-arch-ia64:: binary-arch-ia64-real +build:: build-ia64 +build-ia64:: build-ia64-real +setup:: setup-ia64 +setup-ia64:: setup-ia64-real +binary-arch-ia64-real: + $(MAKE) -f debian/rules.real binary-ar...

Daniel: Thanks for your detailed response. I had seen the discussion from earlier this year, but when I read it, I didn't expect it would be so difficult to get just one bit of information where I wanted it. :-) Thanks for the heads up about clang not necessarily setting ABIname. I have at least enough of that working already that I can generate the appropriate assembly source. After doing a little more investigation, I decided to take an approach that seems simpler than yours, as I'm only trying to solve my own problem. It relies on having things lower in the MC lay...

I am implementing a defined, but currently unimplemented by LLVM, ABI. This ABI differs from an existing ABI in its ELF object format by implementing a subset of an existing ABI, but encoded differently and by setting the e_ident EI_CLASS field. I am trying to use MCTargetOptions::getABIName to set a boolean in the modified subclass of MCELFObjectTargetWriter to indicate which relocation encoding to use. As far as I can determine by source examination and judicious use of a debugger there isn't a simple path from the command line and the setting of ABIname in MCTargetOptions to whe...

Hi. I've been looking at the BTS and PTS and security tracker, and it looks like maybe you could do with some help ? Issues I noticed include: * 4.7, the latest Xen upstream release, is not in sid * Even leaving that aside, sid doesn't seem to have all the security fixes which ought to be expected. * The BTS could do with a bit of gardening, perhaps. Please let me know what, if

Package: xen-3.0 Severity: important Version: 3.0.3-0-2 Tags: sid Hello, I need libxen3.0 and libxen3.0-dev to package libvirt (please see: #384300). Thank you, An?bal Monsalve Salazar -- http://v7w.com/anibal -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url :

...he exception TType encoding being ABI dependant) and I've mixed them together in my original email. The split I should have described is that the label prefix is '$' for O32 and '.L' for N32/N64. Unfortunately O32/N32 are ELF32 and N64 is ELF64. I tried passing MCTargetOptions::ABIName down to the MCAsmInfo but ran into problems with some users of MCAsmInfo not initializing MCTargetOptions. There is also a problem with some users of MCAsmInfo not knowing the ABI. For example, llvm-objdump doesn't know the ABI until it starts reading the object file but has to initialize the M...

....7[1]. You would have to > work around some distro specific things but I tried to keep them at a minimum. > Some things might be useful (like starting qemu for dom0, having xenstored in > its own sysvinit file. the sysvinit dependency hinting). One thing I still have > to fix is to have abiname style changes for the new libs. FWIW, I think I got the library naming cleaned up now (~rc5). Slightly different approach as I had to either keep the major.minor .so versions (I believe because of the map files) or libvirt would fail to compile against the xen lib. -Stefan > > -Stefan &gt...

Package: xen-3 Version: 3.1.1-1 See the transcript below, where I * dpkg-source -x debian/xen-3_3.1.1-1.dsc * add an entry to debian/changelog at the top * run dpkg-buildpackage, which fails I installed the build-dependencies on sid and lenny and the path it's looking for doesn't exist there either. Thanks, Ian. mariner:d> dpkg-source -x ../debian/xen-3_3.1.1-1.dsc gpg:

...-10-23 16:44:45.528956410 -0500 @@ -56,6 +56,9 @@ $(STAMPS_DIR)/build-utils_$(ARCH): DIR=$(BUILD_DIR)/build-utils_$(ARCH) $(STAMPS_DIR)/build-utils_$(ARCH): $(STAMPS_DIR)/setup-utils_$(ARCH) $(MAKE) -C $(DIR)/tools XEN_COMPILE_ARCH=$(XEN_ARCH) XEN_TARGET_ARCH=$(XEN_ARCH) XEN_VERSION=$(VERSION)$(ABINAME) + pod2man $(DIR)/docs/man/xend-config.sxp.pod.5 $(DIR)/docs/man/xend-config.sxp.5 \ + $(DIR)/docs/man/xm.pod.1 $(DIR)/docs/man/xm.1 \ + $(DIR)/docs/man/xmdomain.cfg.pod.5 $(DIR)/docs/man/xmdomain.cfg.5 touch $@ install-base: @@ -96,6 +99,9 @@ install-utils_$(ARCH): DH_OPTIONS = -p$(PACKAGE...

...e.getEnvironment() == llvm::Triple::EABI || - (Triple.getOS() == llvm::Triple::UnknownOS && + (Triple.getOS() == llvm::Triple::NoneOS && Triple.getObjectFormat() == llvm::Triple::MachO) || StringRef(CPUName).startswith("cortex-m")) { ABIName = "aapcs"; @@ -5128,7 +5128,7 @@ if (Str == "x86_64h") T.setArchName(Str); else if (Str == "armv6m" || Str == "armv7m" || Str == "armv7em") { - T.setOS(llvm::Triple::UnknownOS); + T.setOS(llvm::Triple::NoneOS); T.setObjectForma...

[+llvmdev, -llvm-dev] (Oopsies, llvmdev doesn't have a hyphen in it like all the others do) On 6/17/14, 10:45 AM, Jonathan Roelofs wrote: > [+llvm-dev, cfe-dev] > > Was "Re: [PATCH] ARM: allow inline atomics on Cortex M" > > On 6/17/14, 10:42 AM, Jonathan Roelofs wrote: >> >> >> On 6/17/14, 9:35 AM, Renato Golin wrote: >>> On 17 June 2014

Hi, I've been having trouble properly resolving an issue with our assembly syntax. The prefix our assembler uses for private local/global labels depends on the object file format. For ELF32 they begin with '$' and for ELF64 they begin with '.L'. The object file format depends on the ABI, but multiple ABI's are usable with the same target triple so we can't select

...from the ubuntu packaging (thanks, Stefan Bader): - Rebase patches against upstream source (line numbers etc). - debian/rules.real: - Add a call to build common tool headers. - Add a call to install common tool headers. - debian/libxen-dev.install, d/p/ubuntu-tools-libs-abiname.diff: - Add additional modifications for new libxendevicemodel. - debian/patches/tools-fake-xs-restrict.patch: - Re-introduce (fake) xs_restrict call to keep libxenstore version at 3.0 for now. - debian/libxenstore3.0.symbols: add xs_control_command * Rebase patc...

Hi Ian, team, In the week of Feb 23 (time flies!:), we had a very productive day \o/ working on the stretch security/stable package and some irc discussions in oftc #debian-xen which ended with an open end. Ian, you were a bit surprised that 1) my debian-xen repo started with an import of a 4.8 package 2) it was not a git-pbuilder style repo with upstream source included, and asked me to at