Hello,
> > When configuring without --with-arch=armv7-a and using -mthumb flag
> > thumb-1 is been tested.
>
> I don't understand "using -mthumb" . Are you manually adding -mthumb
> to your boot C flags ?
Yes, I'm using:
make bootstrap BOOT_CFLAGS="-O2 -fmodulo-sched
-fmodulo-sched-allow-regmov
== GDB ==
* Committed fix for the GDB part of #620611 (Unable to
backtrace out of vector page 0x) to mainline and
Linaro GDB 7.2.
* Ran into GDB crashes due to memory corruption in tests
involving multiple inferiors. Tracked down root cause
(using valgrind) to long-standin
Hi,
== PandaBoard ==
* upgraded my ARM dev environment from Ubuntu to Linaro snapshot (20110303)
* found another kernel bug on the panda (#728565)
== libunwind ==
* resolved build issues on ARM (when using the linaro snapshot)
* allows the testsuite to work with linkers that do not pull in i
Starting back in Linaro land after a gap of 3-4 weeks where I've been
away on ARM internal tasks.
== GCC ==
- Setting up a new machine that I received for Linaro work.
- Spent some time reviewing upstream patches. Spent some time on the
P1 PR47719 upstream to get this fixed .
- Starting to read u
Hi Revital,
On 4 March 2011 15:46, Revital1 Eres wrote:
> Hello Ramana,
>
>
>> I've always seen this turned on when bootstrapping FSF trunk with no
> special
>> configuration options.
>
> You are correct, sorry for the confusion. I checked again and it is indeed
> turned on also with --with-arch
* Investigated and fixed sqlite3 testsuite failure on ARM (bug 725052)
* Discussing libffi API changes with maintainer; hopefully he's
going to send out his comments today.
* Looking at how to upstream the string routine changes
* Need to look at big endian testing
* Testing QEmu pre-r
RAG:
Red:
Amber:
Green:
Current Milestones:
| Planned| Estimate | Actual |
qemu-linaro 2011-03 | 2011-03-08 | 2011-03-08 ||
Historical Milestones:
finish virtio-system | 2010-08-27 | postponed ||
finish testing PCI p
== This week ==
* Submitted the fix for the Qt miscompilation upstream. Applied after
approval.
* Submitted a patch for the Thumb LDR problem that Dave Martin hit.
This was rejected.
* Ended up spending a few days on the "unreasonable amount of memory
while compiling qemu" bug due to unfa
Hello Ramana,
> I've always seen this turned on when bootstrapping FSF trunk with no
special
> configuration options.
You are correct, sorry for the confusion. I checked again and it is indeed
turned on also with --with-arch=armv7-a.
When configuring without --with-arch=armv7-a and using -mthum
Hello Again,
> I presume this is FSF trunk you are referring to here. I thought this was
> now turned on by default precisely to catch such issues with debug info
early.
>
> I've always seen this turned on when bootstrapping FSF trunk with no
special
> configuration options.
btw, is there a way t
Hello,
> I presume this is FSF trunk you are referring to here. I thought this was
> now turned on by default precisely to catch such issues with debug info
early.
Yes, I'm testing FSF trunk.
Thanks,
Revital
>
> I've always seen this turned on when bootstrapping FSF trunk with no
special
> con
> OK, thanks for your answer. I'll try to see how to resolve it.
> btw, when configuring with --with-arch=armv7-a -gtoggle is
> *not* been used in the bootstrap stages (2 nor 3)
I presume this is FSF trunk you are referring to here. I thought this was
now turned on by default precisely to catch su
Hello,
> >
> > I am looking for a way to disable '-gtoggle' flag in the run of stage 2
in
> > bootstrap; when
> > configuring ARM with (*).
> > The flag seems to be applied in stage 2 but not in stage 3 which seems
to
> > cause bootstrap failure when
> > testing SMS as in stage 2 SMS fails because
On Fri, 2011-03-04 at 15:33 +0200, Revital1 Eres wrote:
> Hello,
>
> I am looking for a way to disable '-gtoggle' flag in the run of stage 2 in
> bootstrap; when
> configuring ARM with (*).
> The flag seems to be applied in stage 2 but not in stage 3 which seems to
> cause bootstrap failure when
Hello,
I am looking for a way to disable '-gtoggle' flag in the run of stage 2 in
bootstrap; when
configuring ARM with (*).
The flag seems to be applied in stage 2 but not in stage 3 which seems to
cause bootstrap failure when
testing SMS as in stage 2 SMS fails because of debug_insn caused
by -
15 matches
Mail list logo
