nce boost by
itself of a few percent, but used a lot of RAM; something cleverer
might be doable that would use less RAM; I don't really know. I don't
think I ever posted the automatic partitioning code; that computer is
off right now, but I can dig out the code if you want to see it.
--
Daniel Jacobowitz
CodeSourcery
for JITs that does exactly
> >that. Is there an equivalent API for linux?
>
> Don't think so.
There isn't really. But I know that other JITs have managed to do this
- I just don't know how. They may use a nasty hack somewhere.
--
Daniel Jacobowitz
CodeSourcery
home page of the
DWARF working group, which includes the version 2 and version 3
standards:
dwarf.freestandards.org/
--
Daniel Jacobowitz
CodeSourcery
Basically, no.
--
Daniel Jacobowitz
CodeSourcery
re interesting results from my testing: it can
sometimes help much more than that - in precompiled header layout.
Depending on the phase of the moon, I saw PCH performance improvements
from 3% to 20%.
--
Daniel Jacobowitz
CodeSourcery
I think that with a reasonable amount of
testing and tuning on different host systems, it might be reasonable to
use it as the default - even if generational collection is disabled by
the lack of mmap.
--
Daniel Jacobowitz
CodeSourcery
artly in malloc() memory, partly in GC
> memory to one of them or by registering additional roots with GC.
Presumably you'd have to register all the GTY()'d roots... I don't know
how that would work out.
--
Daniel Jacobowitz
CodeSourcery
7;ll have to do something like
sort the free list.
This only happens once per zone per collection, so sorting the free
list before releasing pages probably won't add measurable time.
--
Daniel Jacobowitz
CodeSourcery
e - I did not look
very hard) for copying.
--
Daniel Jacobowitz
CodeSourcery
nual, and configuration is step 3.
http://gcc.gnu.org/install/prerequisites.html
--
Daniel Jacobowitz
CodeSourcery
truction, so you have to convert the call to
indirect. It's probably a space loss, stack usage improvement, and I'm
not sure offhand about performance - may be a bit slower.
--
Daniel Jacobowitz
CodeSourcery
to happen here? The description said "calls a
constant function". This:
> int (*fct) (int i);
is of course a function pointer.
--
Daniel Jacobowitz
CodeSourcery
c merge process?
The man to ask about this is DJ Delorie. I'm not sure how much work it
is on his part, though.
Either way it would probably be best to do the initial sync by hand.
And is it really plausible that nothing in src would need updating for
the new intl?
--
Daniel Jacobowitz
CodeSourcery
suggestions as to what products or platforms might cause problems?
No; I'm just surprised that it worked.
--
Daniel Jacobowitz
CodeSourcery
> * MAINTAINERS: Change intl updating instructions.
> > * config.rpath: Copy from GCC tree.
> > * intl: Replace contents of intl directory with intl from GCC tree.
>
> Approved for binutils.
Fine for GDB, too.
--
Daniel Jacobowitz
CodeSourcery
e could easily change the default of the parameter
for ARM, but I assume there are other affected targets. I don't know if we
need the extended region scheduling to be smarter, or if it should simply be
turned off for some targets.
--
Daniel Jacobowitz
CodeSourcery
typedef union
{
struct
On Sun, May 28, 2006 at 08:38:34PM +0200, Thomas Koenig wrote:
> Is anything wrong with SVN, or did my authorization to commit somehow
> fall through the cracks?
Is it maybe an anonymous checkout? Check svn info.
--
Daniel Jacobowitz
CodeSourcery
t; return 0;
> }
Not even a single comment - shame on you both! :-) If this is the
solution we choose, can we make sure that there's at least a comment
explaining what's going on?
--
Daniel Jacobowitz
CodeSourcery
;ll need to modify at least the movqi insn patterns, memory constraints
> and
> the legitimate address stuff. I'm not sure about the clobber, that might need
> additional reload-related machinery.
I suspect it would be better to make GCC do halfword stores instead
(read/modify/write).
--
Daniel Jacobowitz
CodeSourcery
> the PR, too.
It already is. Click "View Bug Activity".
--
Daniel Jacobowitz
CodeSourcery
o support it.
Right - it's the result of __builtin_frame_address (0) we're looking at
here.
Mark's latest change seems logical to me: the user has asked for the
frame address, so hadn't we better arrange that there's a frame?
--
Daniel Jacobowitz
CodeSourcery
. In ARM code the frame pointer is in r11 (when not
> eliminated); in thumb code it is in r7 (because r11 can't be used in
> memory insns).
I'm reading these two paragraphs and the two of you seem to be in
violent agreement. Paul assumed ARM code only.
--
Daniel Jacobowitz
CodeSourcery
t; information.
Which there is no plausible way to do for the ARM EABI, due to ARM's
other choices.
--
Daniel Jacobowitz
CodeSourcery
On Sun, Jun 04, 2006 at 10:29:14AM -0700, Mark Mitchell wrote:
> Daniel Jacobowitz wrote:
> > On Sun, Jun 04, 2006 at 09:54:25AM -0700, Mark Mitchell wrote:
> >> Richard E. asked what possible uses this function might have.
> >> Obviously, GLIBC's backtrace() functi
tkane care of by some
> patches from CodeSourcery. Though, it is possible I may have dreamted.
Nope, it was Nick.
--
Daniel Jacobowitz
CodeSourcery
to be
> standard, you have to go through the committee.
In practice, using string identifiers does make conflicts less likely.
It's also easier for a vendor to pick a unique prefix and be confident
that Apple isn't going to assign some other meaning to
"csl-inline-bart".
--
Daniel Jacobowitz
CodeSourcery
cases should
> be OK with current GGC schemes,
No, it wouldn't be. The collector would try to mark the malloced
memory, and blow up.
--
Daniel Jacobowitz
CodeSourcery
duplicate elimination - your linker can
do that, I hope - it's only larger by a trivial amount.
--
Daniel Jacobowitz
CodeSourcery
On Mon, Jun 12, 2006 at 10:22:17AM -0400, David Edelsohn wrote:
> Typing "make" in the gcc subdirectory does not do what I expect.
Then could you clarify what happens, and what you expect, please?
--
Daniel Jacobowitz
CodeSourcery
he use of hardware debuggers on PC's in bygone years) is to figure
> out what went wrong, and for that purpose you only need to worry
> about the machine/memory state.
Not when you're debugging userspace and you have files.
--
Daniel Jacobowitz
CodeSourcery
On Thu, Jun 15, 2006 at 10:31:55AM -0400, Robert Dewar wrote:
> Daniel Jacobowitz wrote:
>
> >>The point of going backwards (a feature quite familiar to me from
> >>the use of hardware debuggers on PC's in bygone years) is to figure
> >>out what went wrong,
tional unless they are cheap and don't trap. This instruction
> doesn't trap, but it's not cheap.
What metric gets used for this - rtx_cost?
--
Daniel Jacobowitz
CodeSourcery
ded by glibc-devel.
>
> Maybe some one experienced can help you out.
Don't crosspost to gcc and gcc-help, please. This is not a question
about GCC development.
--
Daniel Jacobowitz
CodeSourcery
Please try the other definition, which he clearly meant:
2. Of purely theoretical or academic interest; having no
practical consequence; as, the team won in spite of the
bad call, and whether the ruling was correct is a moot
question.
--
Daniel Jacobowitz
CodeSourcery
t alignment required. */
>
> #define MAX_ALIGNMENT (offsetof (struct max_alignment, u))
I learned while working on the zone collector that there is at least
one platform where this doesn't work, because "long double" had an
alignment of eight on its own and four as a struc
ong double was first which is usually the cures the
> whole struct
> alignment issues.
It's a union. If that makes a difference the platform ABI is
hopelessly broken.
Anyway, I'm thinking of MAX_FIELD_ALIGNMENT or something like that.
--
Daniel Jacobowitz
CodeSourcery
umes a fixed
displacement between segments.
We've implemented something similar to what you need for VxWorks. A
couple of other places had to be changed. I don't remember if the
VxWorks gcc port was submitted, or just the binutils bits.
--
Daniel Jacobowitz
CodeSourcery
bits.
>
> Any chance of this work making it into GCC?
Yes - but we haven't had time to submit it.
--
Daniel Jacobowitz
CodeSourcery
On Wed, Jun 28, 2006 at 03:54:29PM -0600, Shaun Jackman wrote:
> On 6/28/06, Daniel Jacobowitz <[EMAIL PROTECTED]> wrote:
> >On Wed, Jun 28, 2006 at 03:17:30PM -0600, Shaun Jackman wrote:
> >> I'm not terribly familiar with the GCC source tree. I scanned
> >>
nly unnamed arguments? If not, I suspect
this is only for old-style definitions.
--
Daniel Jacobowitz
CodeSourcery
't work. But there's plenty of other ways to write valid code
that won't work!
> Is it really working after all is the real question and I say no it
> can never work correctly on any target.
Obviously untrue. I can't imagine a plausible target where int (*)
(char *) and
e.in".
>
> Perhaps, a quick question on IRC of the correct protocol is
> appropriate?
It is fairly typical to omit the changelog entry in "fix my last patch"
commits. Also in "fix the ChangeLog" commits.
--
Daniel Jacobowitz
CodeSourcery
My rule of thumb: Check the options in automake's generated
Makefile.in.
You probably need a -I path.
--
Daniel Jacobowitz
CodeSourcery
functions, access any visible or virtual members, and pass the pointers
> back into visible functions of the shared object - or even dereference
> the pointers to pass by reference.
So... what does it restrict, then? Is it just defaulting methods to
hidden, as a strange form of access control?
--
Daniel Jacobowitz
CodeSourcery
s shared
object? Either you can access the public members of the class, or you
can't. Being able to access some of them and get link errors on others
is a very strange default interpretation.
--
Daniel Jacobowitz
CodeSourcery
suggest you report this problem to the LSB, since they wrote that
documentation. The documentation is incorrect.
--
Daniel Jacobowitz
CodeSourcery
the next frame. That is, it sounds like
there's something wrong with your generated unwind tables. That's the
usual cause for unexpected end of stack.
--
Daniel Jacobowitz
CodeSourcery
.freestandards.org/en/LSB -> lsb-discuss mailing list?
--
Daniel Jacobowitz
CodeSourcery
accurate and matches the GCC implementation closely.
If it can't dump your FDEs, we probably won't unwind through them
either.
--
Daniel Jacobowitz
CodeSourcery
the c++ -> g++ links remains in the
> Make-lang.in
>
> Ok for trunk when stage1 starts?
Please send patches only to the gcc-patches mailing list. TIA.
--
Daniel Jacobowitz
CodeSourcery
ng else that i need to do.
>
> What options do I have to use when compiling my code?
> Is there any document on this?
This is a list for the developers of GCC. You may get more help on the
gcc-help list.
It sounds like you didn't link with -lpthread.
--
Daniel Jacobowitz
CodeSourcery
ing around)
which only handles the non-branch-delay case. It will still work in a
delay slot, but it's a much heavier-weight operation.
So, until and unless there is a revision of the MIPS architecture on
which this instruction is not guaranteed to trap, I think we should not
put it in a delay slot.
--
Daniel Jacobowitz
CodeSourcery
los has been
working on patches for this. I'm sure it will break a few
unexpected configurations. When it does, we can adjust the behavior as
necessary, or document useful tricks for working with such things in
the manual.
--
Daniel Jacobowitz
CodeSourcery
nd line. It's also possible to
build 32-bit configurations which support 64-bit compilation - but
the default i686-linux configuration does not. The i686-solaris2.10
port does, and Debian's i486-linux compilers do also (local patch).
--
Daniel Jacobowitz
CodeSourcery
. This is a FAQ.
--
Daniel Jacobowitz
CodeSourcery
o wait longer for compilation or has this overhead changed?
They haven't done any measuring I know of, but we needed 64-bit
compilers for a variety of reasons and this was much less disruptive
than packaging a second copy of GCC.
--
Daniel Jacobowitz
CodeSourcery
ot
> accessed and that it will be set before returning, so hush up about
> any uninitialized argument value.
There's more to it than that, unless your compiler is very broken.
GCC should not warn for "int x; foo (&x);".
--
Daniel Jacobowitz
CodeSourcery
s you probably know by now, one can't look at a bug of this sort
without a compilable test case. Andrew correctly pointed out that this
optimization is affected by (for instance) inlining.
--
Daniel Jacobowitz
CodeSourcery
c when generating negation, and there may be macros like
HAVE_negsf2.
Then, the *negsf2 define_insn is used to actually emit the operation
(and for things like combine, which test if an instruction is valid).
--
Daniel Jacobowitz
CodeSourcery
ariables going to the data section. E.g., so
that the resulting executable can find the beginning of that
section and/or make assumptions based on that.
The default is `-fzero-initialized-in-bss'.
--
Daniel Jacobowitz
CodeSourcery
ot; would work!? (modulo suitable
> quote/escaping).
It wouldn't; there's no suitable quoting possible.
--
Daniel Jacobowitz
CodeSourcery
s or something like that.
--
Daniel Jacobowitz
CodeSourcery
descriptor limits, for instance, and
you'll tend to degrade performance.
--
Daniel Jacobowitz
CodeSourcery
I got the impression he was
still open to using it for other things, like types. I may have been
mistaken.
--
Daniel Jacobowitz
CodeSourcery
oo? I think that confusing dwarf-for-types
and dwarf-for-gimple would be a mistake.
--
Daniel Jacobowitz
CodeSourcery
On Fri, Sep 01, 2006 at 10:19:07AM -0400, Kenneth Zadeck wrote:
> Daniel Jacobowitz wrote:
> > On Fri, Sep 01, 2006 at 09:45:34AM -0400, Kenneth Zadeck wrote:
> >
> >> Given that Mark, and for that matter no one else, did not really push
> >> back, I am prett
G_pointer_type would link to a
> DW_TAG_base_type for void (in the case of a void *
> pointer type). Is that not the case?
Void isn't a base type. The DWARF 3 standard way to represent this is
DW_TAG_unspecified_type.
--
Daniel Jacobowitz
CodeSourcery
psulates this knowledge.
If some GCC configuration passes some specific option that is wrong,
then that GCC configuration is broken and a bug should be filed.
--
Daniel Jacobowitz
CodeSourcery
ing at the original example, Kate, what exactly were you confused
about? If it was the "/../lib64" suffix, those are added _after_ the
list of directories to search are decided. They're added when we
consider whether the user asked for -m32 or -m64 (see multilib in the
documentation).
--
Daniel Jacobowitz
CodeSourcery
On Mon, Sep 18, 2006 at 04:36:26PM +0200, Basile STARYNKEVITCH wrote:
> Is the LTO branch inactive now? This surprises me! svn info gives me
Why do you think a data of last Thursday means it is inactive? It
isn't, as you can see if you follow gcc-patches.
--
Daniel Jacobowitz
CodeSourcery
so.1
This is probably pulled in indirectly, from some other system library.
Maybe check with readelf -d if it is directly DT_NEEDED from the
executable?
--
Daniel Jacobowitz
CodeSourcery
time we replaced mips64-sgi-irix6.5, mips64-linux
was changing even faster than it is now. It's settled down quite a
bit; I would be happy to see mips64-linux-gnu on the list now.
--
Daniel Jacobowitz
CodeSourcery
b simulators - and in system mode. However, it doesn't really
make up for testing on hardware. Not unless someone donates a
lot of time to run good hardware certification tests on it, anyway :-)
--
Daniel Jacobowitz
CodeSourcery
ion of the function-like macro
alt_x, which is what is being considered, if I'm reading c99 right,
because no nested replacement of x occurred within the processing
of alt_x(). It's a different scan.
--
Daniel Jacobowitz
CodeSourcery
o approach requesting an addition like this
> to the Dwarf standard, I'm trying my luck here.
You could ask, um, on the Dwarf list... See dwarf.freestandards.org.
--
Daniel Jacobowitz
CodeSourcery
erly clever when they
> configured your gcc package. Normally libdir and libexecdir point to the same
> dir. What output do you see from "gcc -v"?
Not any more. The default changed some time ago. Some distributors
configure them to the same location.
Jeff, for background, up
remove, I
recommend anyone who wants to attempt intl be very very careful. Our
version has a modified build system, and other directories get their
configuration information from it (config/gettext-sister.m4).
--
Daniel Jacobowitz
CodeSourcery
60MB, or about 10% of the repository. If
you've just got the one checkout, the checkouts win. I've got a dozen
right now; from what I've been hearing, svk would be the biggest win
for me.
--
Daniel Jacobowitz
CodeSourcery, LLC
may be exactly what you're suggesting, but could we do this
instead of what we do now?
- Search the registered FDEs
- use dl_iterate_phdr to register and search any unregistered objects
--
Daniel Jacobowitz
CodeSourcery, LLC
n generating release diffs (which are done direct
> from source trees, not with cvs diff) to ensure that diffs to generated
> files that aren't version controlled (and so not handled by gcc_update)
> come after the diffs to their source files.)
This would be about ten lines of shell s
to the "right" one is never an issue. And the
point of the mangling is that the two should be interchangeable anyway.
--
Daniel Jacobowitz
CodeSourcery, LLC
ses are an ELF only manifest, aren't they?
The C++ ABI that GCC follows actually mandates the use of COMDAT. I
doubt that'll make things any easier for you.
--
Daniel Jacobowitz
CodeSourcery, LLC
the suggestion to remove STB_WEAK when munging
> the symbol table. That will work too.
>
> As a side note, can you point me to the C++ ABI that you are refering
> to?
Sure:
http://www.codesourcery.com/cxx-abi/
--
Daniel Jacobowitz
CodeSourcery, LLC
ith an ELF toolchain; use a linker script instead.
--
Daniel Jacobowitz
CodeSourcery, LLC
On Fri, Feb 25, 2005 at 02:22:00PM -0800, H. J. Lu wrote:
> Mainline has
>
> const char version_string[] = "4.0.0 20050225 (experimental)";
>
> Shouldn't it be 5.0 or 4.1?
Mark already changed it to 4.1.
--
Daniel Jacobowitz
CodeSourcery, LLC
n done regularily anyway?
GCC is not designed as a library, so I expect many parts of the
compiler allocate data that does not need to be saved to PCH files
and will live the length of the compilation with xmalloc. I'm sure a
good leak checker could tell you where they are coming from.
--
Daniel Jacobowitz
CodeSourcery, LLC
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 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
pe
ptc by itself. Whether this is the best way or not is up for
discussion, but it's done on purpose :-)
--
Daniel Jacobowitz
CodeSourcery
$argc is pretty new.
It was added in GDB 6.4, released June 2006.
--
Daniel Jacobowitz
CodeSourcery
z $zero,$link
> >
> >
> I am completely missing your question. i do not see any redundancy of
> the insn that you say is redundant. that insn is indexing thru in and
> the next insn is indexing thru res.
>
> Obviously i am missing something.
Except the load from in has been removed (it's redundant); so only the
indexing is left.
--
Daniel Jacobowitz
CodeSourcery
#x27;t believe that the multi-vendor C++ ABI covers the STL. Only
things specifically trying to be compatible with GCC will have the
same members.
--
Daniel Jacobowitz
CodeSourcery
On Tue, Feb 12, 2008 at 07:20:52PM +0100, Hans-Peter Nilsson wrote:
> > Date: Tue, 12 Feb 2008 13:16:27 -0500
> > From: Daniel Jacobowitz <[EMAIL PROTECTED]>
>
> > On Tue, Feb 12, 2008 at 05:13:45AM +0100, Hans-Peter Nilsson wrote:
> > > Thanks to you and Dav
path doesn't exist on the host side.
Ian already mentioned -rpath-link. Just for completeness: -rpath is
only used at runtime, it doesn't even have to be a Unix path. But
the linker may need something else in order to find the libraries
at link time, -L or -rpath-link or both.
--
Daniel Jacobowitz
CodeSourcery
ithout the AltiVec ABI as we do
with it. Which has no affect with -mno-altivec, but requires some
prologue work with -maltivec -mabi=no-altivec. After that, whether
the default ABI is AltiVec or not does not much matter to GCC.
--
Daniel Jacobowitz
CodeSourcery
iVec registers are saved and
restored correctly.
On powerpc-eabi, we would need to dynamically align the stack for
-maltivec to behave.
--
Daniel Jacobowitz
CodeSourcery
k you! I hope we can get these hosted
and maybe hyperlinked somewhere on a permanent basis.
--
Daniel Jacobowitz
CodeSourcery
: "0" (__p) \
> ^^ '0' means forcibly share an input
>operand with operand zero.
That's standard. It just means that if two input operands have the
same value, we can't reuse %0 for the other one.
--
Daniel Jacobowitz
CodeSourcery
but safe
patches changing them are allowed on regression-only branches.
--
Daniel Jacobowitz
CodeSourcery
cc_libexec_prefix?
--
Daniel Jacobowitz
CodeSourcery
401 - 500 of 627 matches
Mail list logo