People keep asking you to take this off the list. Please do so.
--
Daniel Jacobowitz
CodeSourcery
On Fri, Mar 14, 2008 at 10:13:01AM +0100, Basile STARYNKEVITCH wrote:
> So how do I get $(libexecsubdir)/melt-private-include/ from within C code
> of cc1?
Either by replicating code from the gcc driver, or by adding it to
cc1's command line.
--
Daniel Jacobowitz
CodeSourcery
shows the message, and send that to Bugzilla.
--
Daniel Jacobowitz
CodeSourcery
- even if simply because they don't think that it is. In
other words, users do care.
So if the branch is relicensed, maintenance patches for the branch
can no longer be merged into any distributor's (or user's) tree that
cares about this issue.
--
Daniel Jacobowitz
CodeSourcery
> }
>
> Expands into 4 byte stores. Any suggestions on how to implement this?
Try __attribute__((__packed__))?
--
Daniel Jacobowitz
CodeSourcery
he linker script or create an assembly file that
defines it as an absolute symbol with the low bit set, and it
will act as Thumb.
--
Daniel Jacobowitz
CodeSourcery
uch sense... but there you go.
Try clobbering it instead, but you don't even need to since the
pointer is already volatile. asm volatile ("eieio") should work fine.
--
Daniel Jacobowitz
CodeSourcery
#x27;d
never know whether a memory argument should be used for lwz or lwzu.
I think treating =m as generating the output address is unhelpful.
--
Daniel Jacobowitz
CodeSourcery
I don't think. Especially when it changes.
--
Daniel Jacobowitz
CodeSourcery
sually called "classic FP" and dates back long before Book E,
at least to the 601.
--
Daniel Jacobowitz
CodeSourcery
urn;
> }
Note that if buf is a char *, there's no way to know that it's the
start of an object. So you're not testing the same thing they were
talking about; calling foo (&str[2], -1) is completely valid C.
--
Daniel Jacobowitz
CodeSourcery
ets stored somewhere that it
> can be used by the Lisp code.
Yes. Or you can do it without execution in a number of ways, either
by assigning these to constants or using the negative array size error
that autoconf uses to determine sizes by binary search (int foo[4 -
sizeof(int)], et cetera).
--
Daniel Jacobowitz
CodeSourcery
esumably involves further
compilation.
(You didn't say what you are trying to do, so I'm guessing at the
context a bit.)
--
Daniel Jacobowitz
CodeSourcery
ee why
there needs to be an __aeabi_sqrt; sqrt is a function in libm.
--
Daniel Jacobowitz
CodeSourcery
problem :-) Please say what actual
error you've encountered.
--
Daniel Jacobowitz
CodeSourcery
ror message. What is generating any kind of sqrt
libcall? There is nothing in GCC to call __aeabi_sqrt, which AFAIK
does not exist.
--
Daniel Jacobowitz
CodeSourcery
meone could point out where the sqrt function is in
> glibc, on arm.
> Does arm use glibc/sysdeps/ieee754/dbl-64/mpsqrt.c ???
I don't know for sure, but it seems likely. Build glibc with debug
info and step through it?
--
Daniel Jacobowitz
CodeSourcery
The libexec directory is
not in the same relation to bindir that it was at configure time.
You've moved parts of the toolchain pretty much arbitrarily, so it's
not surprising at all to me that it can't find itself...
--
Daniel Jacobowitz
CodeSourcery
rom /usr/app*/bin instead (by following the symlink to the real
binary), it searches /usr/app*/bin/../app*/lib/gcc/wherever. But
cc1's not there.
--
Daniel Jacobowitz
CodeSourcery
On Wed, Apr 16, 2008 at 07:02:30PM +0200, Denys Vlasenko wrote:
> The patch is below. Do you think it makes sense?
No opinion. There is room for confusion about relocation...
--
Daniel Jacobowitz
CodeSourcery
On Wed, Apr 16, 2008 at 09:01:44PM +0200, Denys Vlasenko wrote:
> As I mentined in the first mail, it's not the end of a story.
> Next issue: can't find header files. This used to work with 4.2.1:
Try -v to see where it is searching.
--
Daniel Jacobowitz
CodeSourcery
search dir and you're leaving it
unrelocated in your installation.
--
Daniel Jacobowitz
CodeSourcery
;/../../../../" thing?)
Yes, because that's how the directories are found.
--
Daniel Jacobowitz
CodeSourcery
web site...). They're responding to a problem that
was reported to them, and alerting others to the problem. We can
argue about the details, but not about the need to respond.
--
Daniel Jacobowitz
CodeSourcery
On Mon, Apr 28, 2008 at 09:07:51AM +0200, J.C. Pizarro wrote:
> Excuse me, i'm not the unique and first person that says you stupid,
> GCC did it too.
GCC is not posting on the mailing list. Please be polite to other
contributors; that includes not insulting their intelligence.
up bugs on other targets, so it's better
to run them everywhere.
--
Daniel Jacobowitz
CodeSourcery
;s no tests covering the problems.
CodeSourcery does this all the time.
--
Daniel Jacobowitz
CodeSourcery
ic?
Also check the libgcc configure.host file for your triplet.
--
Daniel Jacobowitz
CodeSourcery
moment.
I'd love to get it working again, at least for native. That can
parallelize tests as fine-grained as you wish, and present consistent logs.
--
Daniel Jacobowitz
CodeSourcery
, so saved %ebp is not at
0(%ebp) yet. That's true at 0xe; at 0xc the saved location of %ebp is
harder to describe. But that won't explain your crashes. The debug
info looks unusual, but correct.
--
Daniel Jacobowitz
CodeSourcery
gisters. Otherwise this
is going to be too order-sensitive.
--
Daniel Jacobowitz
CodeSourcery
How upset is it likely to get on C++
input?
--
Daniel Jacobowitz
CodeSourcery
es for an example; the menu should be before the @include
somewhere.
--
Daniel Jacobowitz
CodeSourcery
includes an ABI supplement. Supplemental to a somewhat hypothetical
document, but there you go...
--
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
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
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
s.google.com/group/generic-abi/browse_thread/thread/5cf669951cb2eef1
--
Daniel Jacobowitz
CodeSourcery
aths:
A /trunk (from /trunk:138076)
undo 138077
--
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
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
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
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
dded to speed up context switching in a kernel application. */
IMO that shouldn't be written in C, then...
--
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
eave the file in the same mode it
was in when the asm was entered.
--
Daniel Jacobowitz
CodeSourcery
that only a convenience for the
implementation of 'target sim'; it's really an independent project.
--
Daniel Jacobowitz
CodeSourcery
7;t
remember the PR.
--
Daniel Jacobowitz
CodeSourcery
GDB.
- What about binding to templates or overloaded functions?
--
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
scope
Nothing pulls in the definition of _U, _N, etc before that point.
I'm sure it's not as broken as it seems, so I must be missing
something... at one point, ./configure --target=i586-mingw32
--with-newlib was all it took.
--
Daniel Jacobowitz
CodeSourcery
insup/cygwin/include/ctype.h
/space/fsf/commit/src/winsup/mingw/include/ctype.h
That third one does not define _U. It uses _UPPER instead. Does this
mean --with-newlib does not work for mingw32? (Note, you can't build
without it either.)
--
Daniel Jacobowitz
CodeSourcery
On Mon, May 07, 2007 at 01:37:51PM -0400, Daniel Jacobowitz wrote:
> That third one does not define _U. It uses _UPPER instead. Does this
> mean --with-newlib does not work for mingw32? (Note, you can't build
> without it either.)
That does appear to be the case. With --with-
On Mon, May 07, 2007 at 07:47:01PM +0200, Paolo Carlini wrote:
> Daniel Jacobowitz wrote:
>
> > The failing command is trying to compile the PCH. This means that
> > we're including a large number of libstdc++ headers in a row. One of
> > the first ones pulls in
w32*)
AC_CHECK_HEADERS([sys/types.h locale.h float.h])
GLIBCXX_CHECK_LINKER_FEATURES
GLIBCXX_CHECK_COMPLEX_MATH_SUPPORT
Those are the "bad" tests.
--
Daniel Jacobowitz
CodeSourcery
really silly typos (like
--with-libs=/usr/i586-mingw32msvc/include <--). So I think
crossconfig.m4 should be fixed for mingw32 to support combined tree
builds, but it's not as big a problem as I thought it was.
I'll take a stab at fixing crossconfig.m4 if I can find a chance.
--
Daniel Jacobowitz
CodeSourcery
ncy on
DW_AT_MIPS_linkage_name is actually a bug in GDB; I worked on this for
a while, but the patches had some rough spots and I never finished
them. I hope I can come back to it some day soon.
--
Daniel Jacobowitz
CodeSourcery
developer convenience, but GCC is a perfectly normal dynamically
linked program and should behave like one IMO.
--
Daniel Jacobowitz
CodeSourcery
ow to answer this question. Bootstrapping is an
unrelated problem, and the compiler is not a vital runtime component
of the system, so its dependencies do not need to be exceptionally
robust in the way that glibc's or even libstdc++'s do. If you were
talking about linking libstdc++ to MPFR I'd have a different story
to tell.
--
Daniel Jacobowitz
CodeSourcery
certainly going
to ship compilers statically linked to MPFR / GMP; we already have
machinery to build them that way. On the other hand I am positive
Debian will not ship its system compiler that way; Debian policy is
quite clear on this, dynamic libraries should always be used.
--
Daniel Jacobowitz
CodeSourcery
to trigger. REG_SAVED_VAL_OFFSET brings us here. Does anyone
see a way to fix this that doesn't involve making context->reg big
enough - and is _Unwind_Word always at least as large as _Unwind_Ptr
(i.e. mode(word) always at least as large as mode(pointer))?
--
Daniel Jacobowitz
CodeSourcery
ardware to magically appear on my door step.
No, qemu has 64-bit support but I don't think it's mature enough to
boot a Linux kernel yet. It might be; Thiemo and Aurelien were
working on it.
--
Daniel Jacobowitz
CodeSourcery
u might make a
mistake.
> Nor am I planning to use libelf: it's too straightforward to find the ELF
> sections I need and to read the ELF header. Use of libelf seems too
> top-heavy,
> although elf.h is very valuable to me.
If you write more complicated tools, you will want libelf later -
you might need to get at relocation data.
--
Daniel Jacobowitz
CodeSourcery
On Thu, Jun 14, 2007 at 02:24:19AM +0530, supriya kannery wrote:
> Is this scenario, of calling backtrace() on a stack containing invalid
> function
> pointer, a supported one?
In my opinion, no. Attach a debugger instead.
--
Daniel Jacobowitz
CodeSourcery
> That said, as none of the routines in question
> > ({eq,ge,le,unord}[sdxt]f2) are actually used by sparc32/sparc64/alpha that
> > use glibc soft-fp code,
Could anyone explain why this change was made? It seems like SItype
would be sufficient everywhere, and I can't see any
sn't make a lick of sense to me. If the type is hidden, how
on earth can it get a member function _of that type_ from another
library? That library would, by definition, have to have a type of
the same name... but it would be a "different" type.
--
Daniel Jacobowitz
CodeSourcery
t this part. The minimum I'd want to
accept this code would be a complete and useful example in the manual;
since Mark and Danny say this happens a lot on Windows, I'm sure there
must be one.
--
Daniel Jacobowitz
CodeSourcery
could you please do so? Thanks.
--
Daniel Jacobowitz
CodeSourcery
why you would want to do
so; and I don't think it has anything to do with aliasing, so it
shouldn't be grouped there.
--
Daniel Jacobowitz
CodeSourcery
n want,
however. They want same shared object, which is what it currently
returns; that's what I think of when you ask me if something binds
"locally", too...
--
Daniel Jacobowitz
CodeSourcery
d be to somehow invent a FILE which wrote to a string. Note that
> gcc's output is just assembler code which is normally passed to the
> assembler; what would you expect to do with that?
On at least glibc systems - I'm not sure if anyone else has this
interface - there's open_memstream.
--
Daniel Jacobowitz
CodeSourcery
64 bit unsigned long?
No, a signed 32-bit integer is always sign extended when promoted to
64-bit. If you have C99 handy, see section 6.3.1.3 (Signed and
unsigned integers).
--
Daniel Jacobowitz
CodeSourcery
;d applaud adding some extra internals
documentation about it, but I think the fact that it's been called
no_new_pseudos for so long suggests that we should just leave it
called that if we want a predicate that means the same thing.
--
Daniel Jacobowitz
CodeSourcery
r's wishes do not come into play.
I believe the key point here is that the FSF does not wish to do so.
--
Daniel Jacobowitz
CodeSourcery
declarations end up in DWARF; take a look at
DW_AT_abstract_origin in the spec.
--
Daniel Jacobowitz
CodeSourcery
n copy,
and only need a location at each inlining site. I'm sure there are
other things we could do with this information, that rely on knowing
what variables are the same from the user's point of view.
--
Daniel Jacobowitz
CodeSourcery
ation is done?
I don't know anything about how this works in GCC; I was describing
how GDB handles it. The blocks don't have any obvious IDs, so
removing blocks with no declarations seems safe to me.
--
Daniel Jacobowitz
CodeSourcery
sounds like you are modelling after the wrong target, a Linux
one when you should be using an ELF one as base instead. You don't
need three CRT files or a separate -static option if you don't have
dynamic linking. And then you don't need to build libgcc with PIC
code in it, and there won't be GOT references any more.
--
Daniel Jacobowitz
CodeSourcery
runtime?
No. You can't generate code in general that works on both!
--
Daniel Jacobowitz
CodeSourcery
namic
linking before you have the linker and execution support ready is
definitely going to be a headache.
--
Daniel Jacobowitz
CodeSourcery
ing option but IIUC STACK_BOUNDARY is.
Why isn't it 64 in the !TARGET_ALTIVEC case with
PREFERRED_STACK_BOUNDARY == 128?
--
Daniel Jacobowitz
CodeSourcery
i386/t-crtstuff anyway. Why didn't it happen? If it does
> override the correct CRTSTUFF_T_CFLAGS, we need this patch. Othewise,
> we need something different.
i386/t-sol2-10 != i386/t-sol2; t-sol2 came first. Looks like you need
to move t-crtstuff up before the Solaris 10 check, maybe?
--
Daniel Jacobowitz
CodeSourcery
ou need anything besides _URC_CONTINUE_UNWIND? The personality
routine in libsupc++ for ARM will return _URC_HANDLER_FOUND even
during forced unwinding but that seems like a bug now that you've
given a meaning to _US_VIRTUAL_UNWIND_FRAME | _US_FORCE_UNWIND.
--
Daniel Jacobowitz
CodeSourcery
7;
> etc binaries for the host is enough, then nothing for the target will be
> required.
This is part of the reason why libgcc no longer lives in the gcc
directory.
--
Daniel Jacobowitz
CodeSourcery
tly handle it?
FWIW, I've come to the opinion that we should just copy the relevant
structure layouts from glibc into gcc and avoid this problem. If the
layout ever changes, we're going to need to handle both in gcc anyway.
--
Daniel Jacobowitz
CodeSourcery
gt; updated files:
>
> col \
> | sed -e 's,\([^:]\)//\(.*\),\1/*\2 */,' \
> -e 's,^//\(.*\),/*\1 */,' \
> | indent
For what it's worth, I wouldn't bother. We can handle minimal changes
from upstream source.
--
Daniel Jacobowitz
CodeSourcery
from some recent autotools upgrade).
I believe this particular error comes from using --enable-shared on a
newlib target.
--
Daniel Jacobowitz
CodeSourcery
ars not to be the case.
Yes, a barrier of some sort is definitely necessary. I believe the
SB1 is weakly ordered, and the architecture spec permits both strong
and weak ordering; but it's been a while since I tried this.
--
Daniel Jacobowitz
CodeSourcery
ded code won't be allowed to use
> any AltiVec instructions.
Well, it would be nice if it worked - since e.g. the GCC testsuite
will try to use it! However, this doesn't affect me directly; I
test the standard powerpc-linux ABI on AltiVec capable hardware,
but I only test -mabi=altivec on our Al
ure to include ports in --enable-add-ons.
> I saw that gcc could be built with unwind support, but default turned off.
LIBUNWIND is not related to this error message.
--
Daniel Jacobowitz
CodeSourcery
ion specifies that everything will look exactly the same
> as if it were a POD with the same members declared in the same order.
I don't think that's true. I believe the non-POD must be passed in
memory, but GCC would be permitted to pass the POD in a register if it
preferred. The layout is defined by the C++ ABI, but not the argument
passing conventions.
--
Daniel Jacobowitz
CodeSourcery
Ds still get passed in
registers if the layout-equivalent POD would, unless there is a
non-trivial copy constructor or destructor; there are non-PODs without
those. Sorry for the confusion.
--
Daniel Jacobowitz
CodeSourcery
ock
I'm sure someone can turn that into a sensible looking example, with a
little inlining.
--
Daniel Jacobowitz
CodeSourcery
arameter. But the enabled alternative seems like a reasonable
addition; ARM has the same problem.
--
Daniel Jacobowitz
CodeSourcery
uch about any problems but file a bug and hope it gets fixed in
> the next release.
Perhaps we should make a prerelease now and call it a Technology
Preview then... :-)
--
Daniel Jacobowitz
CodeSourcery
> dlopen'ed shared libraries at all.
Actually, from context I assume he's talking about pthread_setspecific
and does not know about __thread.
--
Daniel Jacobowitz
CodeSourcery
've been thinking about the bouncing problem quite a bit lately.
I have some rough ideas, but I won't draw out this thread by sharing
:-)
--
Daniel Jacobowitz
CodeSourcery
riables, unless you can explain to the debugger that
the variable is currently in both locations - this has been discussed
but AFAIK there is no representation for it yet. Changing the memory
location won't change the next operation that thinks it's in the
register. Changing the registe
t because this makes GCC much more sensitive
to the correctness of its debugging output!
--
Daniel Jacobowitz
CodeSourcery
r .cpp files will compile just fine.
Please report a bug:
http://gcc.gnu.org/bugs.html
--
Daniel Jacobowitz
CodeSourcery
501 - 600 of 627 matches
Mail list logo