Displaying 20 results from an estimated 9000 matches similar to: "[LLVMdev] Ask for help with FreeBSD bootloader, aka #6627"
2010 Oct 29
3
[LLVMdev] clang -integrated-as compiles all of FreeBSD
hi!
To continue the inflow of good news this week, let me announce that
clang -integrated-as (ie. ELF part of MC) compiles all of FreeBSD!
This includes things like booting kernel, gnu libstdc++, clang/LLVM
itself and many other components that make up FreeBSD operating system.
I personally consider this a milestone where -integrated-as should
become the default for ELF/{x86_64,i386}.
Many
2010 Oct 29
0
[LLVMdev] [cfe-dev] clang -integrated-as compiles all of FreeBSD
On Oct 29, 2010, at 8:45 AM, Roman Divacky wrote:
> hi!
>
> To continue the inflow of good news this week, let me announce that
> clang -integrated-as (ie. ELF part of MC) compiles all of FreeBSD!
>
> This includes things like booting kernel, gnu libstdc++, clang/LLVM
> itself and many other components that make up FreeBSD operating system.
>
> I personally consider
2012 Aug 06
1
[LLVMdev] processFunctionBeforeFrameFinalized setting object offset without effect, stack frame layout wrong
Hi,
Target overrides of processFunctionBeforeFrameFinalized() are misused
in two cases (MBlaze and PowerPC) to set the offsets of objects. Unfortunately
this has no effect because the offsets are immediately reset by
calculateFrameObjectOffsets().
The PowerPC backend does this to setup the stack frame layout according to
the ABI. Ie. it spills the registers etc. in a fixed layout. How to do
2011 Jun 13
1
[LLVMdev] Modifying DAG in TargetLowering::ReplaceNodeResults()
Hi!
I am trying to implement va_arg() on ppc32. Everything went smooth, except
implementing va_arg() of 64bit int. Since i64 is not a legal type on ppc32
DAGTypeLegalizer::ExpandRes_VAARG() splits the va_arg(i64) into two i32
va_args.
The problem with ppc32 va_arg is that it needs special "alignment" of its
gpr pointer when the argument is i64. Ie. I need to know if I am lowering
2009 Mar 13
1
gpxelinux, chain.c32 and the freebsd bootloader
Hi there,
I have some troubles to boot a node with gpxelinux, chain.c32 and a
freebsd (version 7) bootloader installed on the /dev/sda3 part of my
node.
For information, it works fine with pxelinux.
In both cases, the version 3.73 of gpxelinux/pxelinux is used.
My PXE profile :
DEFAULT bootlabel
label bootlabel
KERNEL images_emmanuel/chain.c32
APPEND hd0 3
The message I
2014 Jun 26
2
[LLVMdev] cross-section differences in MC generation
I'm working on Position-independent code for 32-bit PowerPC, but
running into a problem. At the beginning of each function, there's a
pre-word that's the difference between the PICBase (.L1$pb) and the
GOT. This works fine when generating assembly output, but it fails
when generating ELF output, with the error "Cannot represent a
difference across sections" (line 847,
2015 Jan 29
4
[LLVMdev] CPUStringIsValid() into MCSubtargetInfo and use it for ARM .cpu parsing
Tim,
How about the below option ?
1. Specify an existing generic armv7 CPU or the CPU which is close my custom variant. My custom variant can be treated as "cortex-a9" + hwdiv.
So my CPU here is "cortex-a9"
2. Specify the ".arch_extension idiv" which is available as an extension for my custom variant.
3. Teach LLVM & Clang about your CPU's
2016 Nov 18
5
LoopStrengthReduce Code Owner: nominating Quentin
I’d like to nominate Quentin Colombet as LSR code owner. He has handled most of the reviews for me for the past couple years (thanks Quentin), and is willing to take on the responsiblity. Frankly, turning over ownership to Quentin is overdue.
-Andy
2015 Jan 28
2
[LLVMdev] CPUStringIsValid() into MCSubtargetInfo and use it for ARM .cpu parsing
Hi Divacky,
I have an armv7 variant that supports hardware division (extension).
For my variant, I use ".cpu cortex-a9" and division
attribute(.eabi_attribute 44, 2 @ Tag_DIV_use) to let the assembler do the
right thing if it encounters a division instruction.
With your path, the .cpu directive is used to fetch the available features
of a CPU and ignores the eabi attributes.
What
2003 Apr 24
4
ext2 problem
Hello all,
I know this question is (strictly speaking) off topic,
but if someone could at least point me in the right
direction, I would be most grateful.
I have an older system (RH 6.2, overdue for upgrade) with
an ext2 partition that was pushing 99% filled. I did some
space recovery and I have it down to around 90% utilization
now. I have rebooted the unit, and brought it up
single-user
2015 Apr 06
1
Read and publish firmware time stamps and boot time (was: [systemd-devel] bootloader time on a non-EFI bootloader)
[CC?ing coreboot, GRUB, SeaBIOS, Syslinux project and Linux kernel]
Am Montag, den 16.03.2015, 11:38 +0100 schrieb Kay Sievers:
> On Mon, Mar 16, 2015 at 11:29 AM, Umut Tezduyar Lindskog wrote:
> > I would like to pass the time it was spent in bootloader to systemd.
> > Is there a kernel command line to pass this information on non EFI
> > bootloader? Or is there an another
2017 Jul 18
0
Re: [PATCH] v2v: bootloaders: Handle no Bootloader::Tools default section (RHBZ#1472208).
On Tuesday, 18 July 2017 15:57:47 CEST Richard W.M. Jones wrote:
> On Tue, Jul 18, 2017 at 03:46:38PM +0200, Pino Toscano wrote:
> > On Tuesday, 18 July 2017 12:01:12 CEST Richard W.M. Jones wrote:
> > > In SUSE guests, handle the case where
> > > Bootloader::Tools::GetDefaultSection () returns undef.
> > >
> > > Previously this would return an empty
2007 Oct 22
3
Samba "hijack" the connection?
Dear all,
I have 2 domains: JUPITER.COM (Samba 3.0.23c - Centos5) and WIN.COM (Windows
2000 Adv Srv). I join a windows XP SP1 (MOON), first to Windows domain and
then to Samba's.
The problem is when I join the XP to Samba's and then try to logon to WIN.COM,
the XP is instead logon to Samba, thus the username is not found. The DNS is
not a problem, I set the DNS of the XP to
2017 Jul 18
0
Re: [PATCH] v2v: bootloaders: Handle no Bootloader::Tools default section (RHBZ#1472208).
On Tuesday, 18 July 2017 12:01:12 CEST Richard W.M. Jones wrote:
> In SUSE guests, handle the case where
> Bootloader::Tools::GetDefaultSection () returns undef.
>
> Previously this would return an empty string and cause a bogus error
> in subsequent code:
>
> virt-v2v: error: libguestfs error: statns: statns_stub: path must start
> with a / character
> ---
I'm
2017 Jul 18
0
[PATCH v2 1/2] v2v: bootloaders: Handle no Bootloader::Tools default section (RHBZ#1472208).
In SUSE guests, handle the case where
Bootloader::Tools::GetDefaultSection () returns undef.
Previously this would return an empty string and cause a bogus error
in subsequent code:
virt-v2v: error: libguestfs error: statns: statns_stub: path must start
with a / character
---
v2v/linux_bootloaders.ml | 17 ++++++++++++++---
1 file changed, 14 insertions(+), 3 deletions(-)
diff --git
2017 Jul 18
2
Re: [PATCH] v2v: bootloaders: Handle no Bootloader::Tools default section (RHBZ#1472208).
On Tue, Jul 18, 2017 at 03:46:38PM +0200, Pino Toscano wrote:
> On Tuesday, 18 July 2017 12:01:12 CEST Richard W.M. Jones wrote:
> > In SUSE guests, handle the case where
> > Bootloader::Tools::GetDefaultSection () returns undef.
> >
> > Previously this would return an empty string and cause a bogus error
> > in subsequent code:
> >
> > virt-v2v:
2017 Jul 28
0
Re: [PATCH v2 1/2] v2v: bootloaders: Handle no Bootloader::Tools default section (RHBZ#1472208).
On Fri, Jul 28, 2017 at 10:02:34AM +0200, Pino Toscano wrote:
> On Tuesday, 18 July 2017 19:59:20 CEST Richard W.M. Jones wrote:
> > In SUSE guests, handle the case where
> > Bootloader::Tools::GetDefaultSection () returns undef.
> >
> > Previously this would return an empty string and cause a bogus error
> > in subsequent code:
> >
> > virt-v2v:
2008 Jul 30
2
[PATCH] [XM] Enable a bootloader when using XM via Xen-API
This enables the usage of a bootloader, i.e., pygrub, when starting a
domain using xm in Xen-API mode.
Signed-off-by: Stefan Berger <stefanb@us.ibm.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
2011 Apr 28
3
ETA
Dear developers,
I don't care for reasons, arguments, or flamefests. I need to plan my
workload.
By now I have half a dozen servers overdue for reimaging. I can put this
off for another week or two, but not really much longer.
There's obviously no point in installing centos 5 on any new machine.
So I need to know: is there any point in my waiting another week, or
should I just say
2009 May 18
2
centos 5.2 install: mbr or no bootloader ?
I recently used a purchased centos 5.2 dvd to install.
It all went smoothly, and I am up and running
automagically it seems to have upgraded itself to 5.3 Final
One peculiarity:
I believe I was given the choice of:
--installing the bootloader into mbr
or
--no bootloader install
I did not want my mbr overwritten, so I chose no bootloader
Why is there no choice of 1st sector of root partition?