On Fri, Apr 13, 2012 at 4:04 AM, Richard Guenther
wrote:
> Heh - that's what I do for years, too ;) I suppose sth crashes on the server
> side when you save the page, so the communication is broken mid-way.
I haven't looked at this in ages, but for GDB we had a problem with
mail notifications be
Sorry for being late to the party.
On Wed, Feb 15, 2012 at 9:55 AM, Ian Lance Taylor wrote:
> Ouch, I did not know that the EABI left this open. That seems like a
> bug, because it prevents code from being interoperable. This is
> precisely the kind of thing an ABI should address. Does anybody
On Mon, Aug 29, 2011 at 11:18 AM, Ken Werner wrote:
> On 08/25/2011 02:26 PM, Andrew Haley wrote:
>>
>> Throwing an exception through a segfault handler doesn't always work
>> on ARM: the attached example fails on current gcc trunk.
>>
>> panda-9:~ $ g++ segv.cc -fnon-call-exceptions -g
>> panda-9
we still need 4.3?
--
Daniel Jacobowitz
in general, dislikes duplicated source code in packages, but I
don't know if they care when the duplicated bits are non-GNU. There
were definitely GDB developers that disliked bundling expat, so
perhaps you can find the reasons in the archives.
--
Daniel Jacobowitz
CodeSourcery
t; is deleted as dead code when optimization is enabled.
No, this is incorrect. The issue must be specific to modification of
read-only data.
--
Daniel Jacobowitz
CodeSourcery
ant to be, or simply a temporary
> shortcoming? Have i missed an obvious kludge?
My two cents, but that looks exactly right to me. Passing the float
to printf is going to convert it to a double and it will be printed as
a double, so you're unexpectedly adding double-precision operations t
want to make the breakpoint pending? If it did,
say yes. If it didn't, try a newer version of GDB.
--
Daniel Jacobowitz
CodeSourcery
same as before, I would think.
Not the peripheral, just one register. e.g. you might read a control
register into a struct of the same (32-bit) type, and then read
multiple fields from the copied struct.
--
Daniel Jacobowitz
CodeSourcery
out assertions, not
directives. Something like this:
mov r0, r1 @ [length 2]
add ip, lr, ip @ [length 4]
mov r0, r1 @ [length 4] <-- assembler error 'insn has length 2'
GCC can output length information, but it is never exact, and it is
not in a form recognized by the assembler.
On x86, I have no idea how this would work.
--
Daniel Jacobowitz
CodeSourcery
g to do.
FWIW, my opinion (and I think Jakub has expressed a similar opinion
and/or tool in the past) is that there is a sane way to do this: put
assertions in the assembler output and have the assembler validate
them.
On the other hand, I'm not going to argue that it's a lot of work.
--
Daniel Jacobowitz
CodeSourcery
without optimization. There's some unique GDB tests
that use this. It causes them to be live between statements in a
machine register instead of always stored in stack slots.
This might not be current information though.
--
Daniel Jacobowitz
CodeSourcery
just a parser and a syntax tree).
--
Daniel Jacobowitz
CodeSourcery
d are "externally visible".
Then you can think about it as "does not alias any non-device
memory", or any number of variants on that.
--
Daniel Jacobowitz
CodeSourcery
to tears if they're both outputs.
Hrm. Yeah, those really should be two pseudos. I'll fix that.
--
Daniel Jacobowitz
CodeSourcery
On Fri, Apr 02, 2010 at 12:06:28AM +0100, Bernd Schmidt wrote:
> On 04/01/2010 10:54 PM, Daniel Jacobowitz wrote:
> > I'm debugging a Thumb-2 glibc build failure on trunk for
> > arm-none-linux-gnueabi. I believe it's from Richard Earnshaw's
> > 2010-02-01 pa
ICE
trying to emit (set (const) (reg)).
It seems to me that the problem is marking a register in the RHS of a
set as an output constraint. The reg becomes function_invariant_p and
chaos ensues.
Is this right? If so, is there somewhere that should assert if an
operand's constraint is marked as an output, but not somewhere that
the RTL allows modification of the operand?
--
Daniel Jacobowitz
CodeSourcery
;s a prototype:
http://sourceware.org/ml/gdb-patches/2006-10/msg0.html
--
Daniel Jacobowitz
CodeSourcery
for now at least. Too bad.
Despite all that exchange, I don't think you ever answered Andreas's
question - at least not in a way that I could understand. A size of
what? The size of the *type* on x86 is 16; the size of the *data
bits* is 10. But what cares about the size of the d
any support for shared libraries. It
will ignore profiling samples that lie outside the executable. And in
this case, that includes _mcount (which is in libc.so.6). That's
probably why.
--
Daniel Jacobowitz
CodeSourcery
you even know what the registers
are.
--
Daniel Jacobowitz
CodeSourcery
tion to select alternatives; (C) branch shortening to
determine branch alternatives.
I'm curious if anyone thinks there's a generic solution to this (that
doesn't involve a complete instruction selection rewrite :-).
--
Daniel Jacobowitz
CodeSourcery
port for o32 entirely.
I don't think anyone's suggested that. o32 is the default ABI for
32-bit MIPS GNU/Linux targets which are still in wide use.
--
Daniel Jacobowitz
CodeSourcery
can also ignore it.
--
Daniel Jacobowitz
CodeSourcery
of host systems where shell scripts aren't a viable
option for ld. Why make everyone write the wrapper script? Makes
sense to me to have gcc decide.
--
Daniel Jacobowitz
CodeSourcery
the 64-bit insns
> it still fails the openssl testsuite.
Interesting, I knew you had a lot of Cirrus patches but I didn't
realize the state of the checked-in code was so bad.
Is what's there useful or actively harmful?
--
Daniel Jacobowitz
CodeSourcery
h weird operand predicates. For instance,
in a patch I'm working on for ARM cmpdi patterns, I ended up needing
"cmpdi_lhs_operand" and "cmpdi_rhs_operand" predicates because Cirrus
and VFP targets accept different constants. Automatically generating
that would be a bit excessive though.
--
Daniel Jacobowitz
CodeSourcery
For the sake of conversation I'll call them Alice and
Bob... no, I'll call them TARGET_MAVERICK and TARGET_NEON. Now you
need a minimum of three copies of the mov pattern that are
mostly the same.
It'd be nice if there was a way to compose instruction patterns :-(
--
Daniel Jacobowitz
CodeSourcery
se EPILOGUE_USES to say that changes to the
accumulator should not be discarded. You could also use
unspec_volatile instead of unspec, but that may further inhibit
optimization.
--
Daniel Jacobowitz
CodeSourcery
at and how do I handle the cost then ?
>- Just say that an unspec has a higher cost?
Are you really talking about rtx_costs? It sounds to me more like you
want to change your scheduler.
--
Daniel Jacobowitz
CodeSourcery
tion
>
> However, the solution seems to work, except in O0, where I get this error:
This means whatever is calling gen_newrtl to create the insn is not
checking operand predicates first. That's probably code you wrote
too.
--
Daniel Jacobowitz
CodeSourcery
esn't. You may have heard of a commercial testsuite built on this
principle :-)
--
Daniel Jacobowitz
CodeSourcery
blems. Do you have a concrete problem?
> Is the implementation still incomplete?
No. It's been finished for two years or more.
--
Daniel Jacobowitz
CodeSourcery
ntation caller and __aeabi_read_tp() must run in
> the same mode.
I don't believe that this is true. In what way is it not safe?
--
Daniel Jacobowitz
CodeSourcery
On Wed, Nov 25, 2009 at 08:31:27PM +0100, Richard Guenther wrote:
> And patch doesn't have an option to ignore whitespace changes.
Sure it does. -l (for loose, or --ignore-whitespace).
QUILT_PATCH_OPTS for quilt.
--
Daniel Jacobowitz
CodeSourcery
ling for other vector sizes.
> >3) Switch to the new mangling
>
> I vote for 2.
Does anyone know of another relevant compiler? What does it do?
For instance, if someone can hand me a test case, I could check how
ARM's compilers mangle it (or don't).
--
Daniel Jacobowitz
CodeSourcery
his?
>
> The color that spells -fuse-linker-plugin seems better, in line
> with other options. How it's implemented, especially regarding
> having to ignore it in middle-end is unimportant wrt. spelling,
> IMVHO.
I agree with H-P.
--
Daniel Jacobowitz
CodeSourcery
other
> functions are not considered to be called once, perhaps a visibility
> issue. We also should say what limit was reached on inlining hlprog.
Maybe because of whatever did that cloning?
--
Daniel Jacobowitz
CodeSourcery
nostics are only of
> limited use without (say) #pragma unroll.
Not too limited, I'd say. I've seen a lot of developers willing to
mutilate their critical loops to accomodate the compiler.
--
Daniel Jacobowitz
CodeSourcery
o put them into a separate
> file so the linker won't produce undefined references when they are not
> actually used by lto1.
Yes. Take a look at config/arm/arm-c.c, which does not go into
libbackend.a.
--
Daniel Jacobowitz
CodeSourcery
eally aimed at compiler developers. I think we would
benefit from more "what is the compiler doing to my code" options
(producing "note:"); things like which functions were inlined, which
loops unrolled. We do already have this for vectorization.
--
Daniel Jacobowitz
CodeSourcery
On Wed, Oct 07, 2009 at 04:29:29PM +0200, Basile STARYNKEVITCH wrote:
> I suppose LTO plugins means plugin dlopen-ed in lto-plugin/lto-symtab.c
It sounds to me like this confusion comes from "LTO plugins". Isn't
it just "LTO plugin"? That is, a specific pl
" links at the above
> URLs) these appear to have genuinely originated at rt.gnu.org via the web
> interface:
Isn't this more likely the RT admins closing spam reports?
--
Daniel Jacobowitz
CodeSourcery
d out where to look for a functional version of the gcc
> cross compiler for this cpu.
If you can't build GCC for your target, I suggest you either use a
help list for that purpose (gcc-help or the crosstool or buildroot
lists), or find a pre-compiled ARM Linux toolchain.
--
Daniel Jacobowitz
CodeSourcery
sfully pick up files from another
directory?
--
Daniel Jacobowitz
CodeSourcery
On Thu, Jul 09, 2009 at 03:45:52PM +0200, Basile STARYNKEVITCH wrote:
> Daniel Jacobowitz wrote:
> >On Thu, Jul 09, 2009 at 03:01:01PM +0200, Basile STARYNKEVITCH wrote:
> >>In simpler words, *.so have to be compiled with -fPIC, and libiberty
> >>is not compiled with -
ibiberty on any platform supporting plugins should not suffer
from this problem.
If you're concerned about it, then build a subset. I've considered a
separation of libiberty into replacements and utilities, anyway.
--
Daniel Jacobowitz
CodeSourcery
ur plugin and get make_temp_file that way.
--
Daniel Jacobowitz
CodeSourcery
define __extension__
(gdb) p __extension__ 1
$1 = 1
That's all that's necessary; it's used to suppress warnings.
Statement expressions, on the other hand, are right out. I can't see
any practical way to teach GDB about that.
--
Daniel Jacobowitz
CodeSourcery
just do the tracking inside of the prologue or for register
> variables, those that are stored into memory during the prologue and live in
> memory shouldn't be tracked outside of the prologue at -O0.
I completely agree, this would make GDB more useful.
--
Daniel Jacobowitz
CodeSourcery
n it may appear from the
release date, since it branched off of mainline five years ago. A lot
has changed since then.
--
Daniel Jacobowitz
CodeSourcery
does
not), we'd have a problem: the 'qN' registers are two 'dN' registers
concatenated, and GCC only knows about them once.
--
Daniel Jacobowitz
CodeSourcery
gcc-patches/2009-04/msg01860.html
--
Daniel Jacobowitz
CodeSourcery
and/or be useless with most
GCC 4.x binaries. For instance, in that time we added location list
support.
--
Daniel Jacobowitz
CodeSourcery
is would be quite useful.
--
Daniel Jacobowitz
CodeSourcery
nces that
> contradict each other and later give links to (or quote) the context?
> I am having troubling identifying the contradiction.
Please, could you not do it on this list?
A discussion about the differences between LLVM and libjit is wildly
off-topic for GCC development.
--
Daniel Jacobowitz
CodeSourcery
x27;s what I said. This is how the uClibc and GLIBC dynamic
loaders work and I believe it's described in Ulrich's paper.
--
Daniel Jacobowitz
CodeSourcery
On Tue, Mar 17, 2009 at 04:03:45PM +0100, Joel Porquet wrote:
> 2009/3/17 Daniel Jacobowitz :
> > On Tue, Mar 17, 2009 at 10:26:05AM +0100, Joel Porquet wrote:
> >> I don't understand how the runtime loader could know that! As far as I
> >> know, the tls model is n
hile(*str)
> *tty = *str++;
> }
If you believe there is a bug, and you have a testcase, please report
it in bugzilla. Thanks.
--
Daniel Jacobowitz
CodeSourcery
On Mon, Mar 16, 2009 at 06:19:01PM +0100, Joel Porquet wrote:
> 2009/3/12 Daniel Jacobowitz :
> > On Thu, Mar 12, 2009 at 02:02:36PM +0100, Joel Porquet wrote:
> >> > Check what symbol is at, or near, 0x4003 + 22368. It's probably
> >> > the GOT plus a c
for
>
> [...]
>
> > Can anyone clarify if the SC *really* need us to not branch before the
> > license change, as opposed to merely not /release/ until then?
>
> The topmost sentence should be unambiguous. Yes, the SC asked us not
> to branch.
But:
> (And why, if so?)
--
Daniel Jacobowitz
CodeSourcery
f the symbol. This
> name then allows to look up the symbol. Unfortunately, in the case of
> local-dynamic, ELF_R_SYM will return 0 which is not correct (the same
> for global-dynamic will return 9): we can see by the way that readelf
> is not able to get the symbol name. What do you thi
32768==0x8000.
Are you sure both of those code sequences are calling __tls_get_addr?
If so, compare the arguments they passed.
> Last question, is there a difference between DSO and PIE objects other
> than the INTERP entry in the program header?
Yes. Symbol preemption is allowed for DSOs but not for PIEs or normal
executables. That explains the different choice of model.
--
Daniel Jacobowitz
CodeSourcery
haven't written C++ in a while, so forgive any obvious gaffes.
class X {
int x, *y;
X() {
y = &x;
}
X(X &obj) {
x = obj.x;
y = &x;
}
}
Memcpy that somewhere else and the internal pointer is invalid.
--
Daniel Jacobowitz
CodeSourcery
* slower, please report it as a bug in
Bugzilla.
--
Daniel Jacobowitz
CodeSourcery
s a static variable, then
> multiple translation units require access to the static variable. That
> does not imply that the static variable has external linkage.
Does this mean that if you compiled some of those TUs with GCC, and
some with icc, they might legitimately access different copies of the
static variable? Seems odd.
--
Daniel Jacobowitz
CodeSourcery
.
Did you try mips-unknown-linux-gcc -EL -print-search-dirs?
--
Daniel Jacobowitz
CodeSourcery
nner
RTX. Search arm_rtx_costs_1 for "CONST_INT:".
--
Daniel Jacobowitz
CodeSourcery
t cases where 4.0.2 gives smaller code with -Os
than a 4.4 snapshot, please, file them in bugzilla.
--
Daniel Jacobowitz
CodeSourcery
centralized, and (B) standardized. Otherwise the right way to pass
arguments will end up different for every plugin.
--
Daniel Jacobowitz
CodeSourcery
nding warning would be a win? "warning: ignored NULL check
because pointer has already been dereferenced"?
--
Daniel Jacobowitz
CodeSourcery
? And the tests use
> that rather than testing for a specific CPU model?
This doesn't answer what you should do now, but I can explain the
precedent: the only reason there is a predefine for 405 is so that the
atomicity routines in libstdc++ know to avoid lwsync.
--
Daniel Jacobowitz
CodeSourcery
nop
> 5ffe14bc: 8000sdc3$31,-32768(ra)
>
> We can see that the offsets are prefixed by 8. Why is that?
The offsets are biased; that's -32768, the lowest 16-bit signed
offset. The bias is used to expand the addressable range of the
thread pointer.
Glad I could help!
--
Daniel Jacobowitz
CodeSourcery
r four words. The second and fourth words will be
the offsets. This is a global dynamic sequence, since it passes
non-zero offsets to __tls_get_addr.
--
Daniel Jacobowitz
CodeSourcery
tant.
This is all very interesting, but you didn't answer my question: is
this causing some problem, or just confusing? These are all intended
optimizations.
--
Daniel Jacobowitz
CodeSourcery
R_MIPS_TLS_DTPREL type with the
> R_MIPS_TLS_DTPMOD, since for each tls variable in global dynamic
> model, tls_get_addr must receive the module index and the offset. Here
> is the second problem...
That's because this is the local dynamic model.
--
Daniel Jacobowitz
CodeSourcery
On Fri, Oct 31, 2008 at 01:02:18PM -0400, Jack Howarth wrote:
>Can anyone explain if the recent change in Apple dropping their
> NDA will have any impact on the GPLv3 issue with Apple and FSF?
Please discuss this on some more appropriate forum, not here.
--
Daniel Jacobowitz
CodeSourcery
that r77 is not used in it's function after this instruction
> and thus DCE deletes it.
Don't focus on DCE. That's not the problem; the fact that there's no
visible dependence is the problem. Can you make the next instruction
have a use for r77 explicitly (CALL_INSN_FUNCTION_USAGE)?
--
Daniel Jacobowitz
CodeSourcery
On Sun, Oct 12, 2008 at 03:13:47AM +0800, Zhang Le wrote:
> On 00:06 Sat 11 Oct , Daniel Jacobowitz wrote:
> > > If this is ok, I will post a little patch.
> >
> > That sounds fine, but the whole process is trouble.
>
> Would you explain why it is trouble? Tha
work. The first step
in cross building a native compiler like this is to build a cross
compiler of the right version.
> If this is ok, I will post a little patch.
That sounds fine, but the whole process is trouble.
--
Daniel Jacobowitz
CodeSourcery
On Mon, Sep 29, 2008 at 03:10:28PM +0100, Joern Rennecke wrote:
> To give it a bit more legal bite
There are no lawyers on this list (that I'm aware of). If you want to
discuss this, please contact the FSF or SC directly instead. It does
no good here.
--
Daniel Jacobowitz
CodeSourcery
GDB.
- What about binding to templates or overloaded functions?
--
Daniel Jacobowitz
CodeSourcery
7;t
remember the PR.
--
Daniel Jacobowitz
CodeSourcery
that only a convenience for the
implementation of 'target sim'; it's really an independent project.
--
Daniel Jacobowitz
CodeSourcery
eave the file in the same mode it
was in when the asm was entered.
--
Daniel Jacobowitz
CodeSourcery
cts must complete in-order. GCC will not move code past a volatile
> operation.
It's still not sufficient without a memory barrier.
--
Daniel Jacobowitz
CodeSourcery
dded to speed up context switching in a kernel application. */
IMO that shouldn't be written in C, then...
--
Daniel Jacobowitz
CodeSourcery
add
> GUALCHK* annotations (or with separate compilation, if some stuff is
> moved into a separate header).
FWIW, I think this is a good approach.
--
Daniel Jacobowitz
CodeSourcery
glibc homepage.
>
> 2.8 is not an official final release yet.
That's incorrect; the glibc maintainers just don't care much for
tarballs. You can find the tag in CVS from several months ago.
--
Daniel Jacobowitz
CodeSourcery
them. I'll try to have
> a look at the patches over the weekend.
No problem, and thank you for looking at them - and for your patches;
I'm really pretty happy with the combined work.
--
Daniel Jacobowitz
CodeSourcery
On Thu, Jul 24, 2008 at 12:16:20PM -0400, Daniel Jacobowitz wrote:
> I have attached
Let's all pretend I attached this glibc patch, instead of the one in
my previous message, please.
--
Daniel Jacobowitz
CodeSourcery
2008-07-24 Mark Shinwell <[EMAIL PROTECTED]>
Daniel Jacob
aths:
A /trunk (from /trunk:138076)
undo 138077
--
Daniel Jacobowitz
CodeSourcery
s.google.com/group/generic-abi/browse_thread/thread/5cf669951cb2eef1
--
Daniel Jacobowitz
CodeSourcery
d -mno-shared will probably show the same
problem.
> Does anyone have any idea how this has broken, and how to work around
> / fix this in gcc or mklibs?
You'll have to make mklibs ignore this symbol; the linker defines it.
--
Daniel Jacobowitz
CodeSourcery
an idea.
Your version looks fine to me, it's ABI-preserving, the PLT entries
still work for MIPS I and still have the same runtime cost when not
resolving. I like it - thanks!
I'm not worried about making people upgrade objdump, either.
--
Daniel Jacobowitz
CodeSourcery
it, I won't argue with you about stepping down, but
please don't because of this incident.
[In any case, I'd decline; I'm trying to shed some of my existing
maintenance responsibilities so that I can spend more time on the ones
I care most about. Anyone else want to be binutils release manager?]
--
Daniel Jacobowitz
CodeSourcery
includes an ABI supplement. Supplemental to a somewhat hypothetical
document, but there you go...
--
Daniel Jacobowitz
CodeSourcery
es for an example; the menu should be before the @include
somewhere.
--
Daniel Jacobowitz
CodeSourcery
How upset is it likely to get on C++
input?
--
Daniel Jacobowitz
CodeSourcery
gisters. Otherwise this
is going to be too order-sensitive.
--
Daniel Jacobowitz
CodeSourcery
1 - 100 of 627 matches
Mail list logo
