"Satendra Pratap " <[EMAIL PROTECTED]> writes:
Please don't send mail to so many mailing lists. In particular
[EMAIL PROTECTED] is not a mailing list, and I've dropped it from the CC.
> ** Legal Disclaimer
> "This email may contain confidential an
Satendra Pratap <[EMAIL PROTECTED]> writes:
> I can not control the disclaimer that is being appended by our office
> mailserver . Hence resending the mail from my gmail account.
Thanks.
> After all this I got down to breaking the problem into a
> compiler/linker (or my understanding) issue. Aft
"Dave Korn" <[EMAIL PROTECTED]> writes:
> CONSTRUCTORS is only valid for formats such as ECOFF and XCOFF. Read the
> bit in the ld manual more closely:
>
> ---
> `CONSTRUCTORS'
> [ ... ] When linking object file formats which do not support
>
"Joseph S. Myers" <[EMAIL PROTECTED]> writes:
> In particular, I'm surprised at the Darwin configurations apparently
> not defining NO_IMPLICIT_EXTERN_C, and at most OpenBSD configurations
> not doing so (but alpha-openbsd gets it from alpha/alpha.h); VxWorks
> configurations are also inconsistent
Joe Buck <[EMAIL PROTECTED]> writes:
> On Tue, May 10, 2005 at 02:26:12PM -0400, Ian Lance Taylor wrote:
> > How would people feel about adding a configure option
> > --with-implicit-extern-c? Then we could justifiably flip the default
> > for the generic *-elf,
Vasanth <[EMAIL PROTECTED]> writes:
> I am working on a port of GCC to a 32-bit RISC machine. I am having
> trouble with .combine pass adding clobbers to instruction patterns. To
> be more specific,
>
> (define_insn "lshrsi3_internal_reg_nohwshift"
> [(set (match_operand:SI 0 "register_operand"
"Vasanth Asokan" <[EMAIL PROTECTED]> writes:
> Quoting from the description of (clobber x),
>
> ### If the last group of expressions in a parallel are each a clobber
> expression whose arguments are reg or match_scratch (see section 10.4
> RTL Template) expressions, the combiner phase can add the
Florian Weimer <[EMAIL PROTECTED]> writes:
> Are there any objections to exporting structure layout from GCC, in a
> format which can be parsed in a straightforward manner? Such a patch
> could be used as a GPL circumvention device, but I'm not sure how
> relevant this is in practice because GCC
"Gary Funck" <[EMAIL PROTECTED]> writes:
> Given a binary distibution of GCC, for example, built to install under
> /usr/local, is it possible to configure and build the compiler in such a
> way that a binary packaging method such as RPM can allow a user to specify
> an alternate installation poin
"Gary Funck" <[EMAIL PROTECTED]> writes:
> Does the -static switch play any role during compilation, or is it
> a link-only switch?
It is a link-only switch.
> A quick review of gcc.c, indicates that -static
> may play a role on some targets:
>
> /* %{static:} simply prevents an error message
"Gary Funck" <[EMAIL PROTECTED]> writes:
> Ian Lance Taylor wrote (in part):
> > In fact many targets compile code differently depending upon whether
> > the code is to be put into a shared library or not, but this is
> > controlled via options like -fpic, n
"Dams, Dennis \(Dennis\)" <[EMAIL PROTECTED]> writes:
> I'm trying to use the -fdump-translation-unit option (gcc (GCC)
> 4.1.0 20050505 (experimental)), but it does not seem to do
> anything. What's the right way to use it - should I specify any
> additional switches/options?
-fdump-translation-
"Gary Funck" <[EMAIL PROTECTED]> writes:
> Ian Lance Taylor wrote (in part):
> > Telling the dynamic linker about a dynamic libgcc is still a problem,
> > but that is a problem whereever you put the compiler.
>
> If I'm not interested in build a dynami
Mark Mitchell <[EMAIL PROTECTED]> writes:
> Anyhow, why do we install libiberty.a, but not the libiberty include
> files?
I expect this dates back to the time when libiberty was mainly just a
replacement for missing system functions, and there were no particular
header files associated with it.
Gabriel Dos Reis <[EMAIL PROTECTED]> writes:
> The file libiberty/xstrerror.c contains the following fragment
>
> #ifdef VMS
> #include
> #if !defined (__STRICT_ANSI__) && !defined (__HIDE_FORBIDDEN_NAMES)
> extern char *strerror (int,...);
> #define DONT_DECLARE_STRERROR
>
"zouq" <[EMAIL PROTECTED]> writes:
Please don't start a new thread by replying to a message on an
existing thread. Just send a new message, instead. Otherwise your
message goes in the wrong place for people who use threaded e-mail
readers.
> i am trying to port a front end to gcc,
> and i am co
"zouq" <[EMAIL PROTECTED]> writes:
> yes, as you have suggested, i have already read the gcc-int about garbage
> collection, and i still can`t get the imformation i want.
> i want to know the following constructs:
> gt_ggc_cache_rtab, gt_ggc_deletable_rtab
> acording to what rules to genenrat
"zouq" <[EMAIL PROTECTED]> writes:
> in the gt-c-decl.h,
> three functions about lang_decl,
> gt_pch_nx_lang_decl(),gt_ggc_mx_lang_decl, gt_pch_g_9lang_decl(),
> what are the differences between the three functions?
The _nx_ functions fill in the pchw field of ggc_root_tab. This is used
when sav
Richard Guenther <[EMAIL PROTECTED]> writes:
> /net/alwazn/home/rguenth/src/gcc/cvs/gcc-4.1/gcc/testsuite/gcc.dg/compat/generate-random.c:55:23:
> libiberty.h: No such file or directory^M
> /net/alwazn/home/rguenth/src/gcc/cvs/gcc-4.1/gcc/testsuite/gcc.dg/compat/generate-random_r.c:56:23:
> libibe
Andreas Schwab <[EMAIL PROTECTED]> writes:
> Ian Lance Taylor writes:
>
> > Richard Guenther <[EMAIL PROTECTED]> writes:
> >
> >> Note how
> >> 1. it uses $(CC) for building, not the built compiler
> >
> > That is correct, as this p
Richard Guenther <[EMAIL PROTECTED]> writes:
> It works after removing the libiberty includes from generate-random.c
> and generate-random_r.c
Personally I think this change comes under the "obvious" rule, given
Mark's change yesterday to not link against libiberty.
Ian
Mark Kettenis <[EMAIL PROTECTED]> writes:
>From: Ian Lance Taylor
>Date: 15 May 2005 23:20:14 -0400
>
>
>Well, we require an ISO C90 compiler; do we require ISO C90 libraries?
>If we require the libraries, then we can remove a number of files from
ttribute. Always with an again randomly appended character
> at the
> end of the macro name in the error message.
>
> At first glance it appears like a string null termination problem so I've
> added:
Sorry about that. Braino on my part. I'm committing this patch as
t
"Ling-hua Tseng" <[EMAIL PROTECTED]> writes:
> I have tried to adjust the constraints to 'r' (general registers) for
> the "movv4qi" and "addv4qi" insn patterns,
> but I got the same problem.
What about HARD_REGNO_MODE_OK?
Ian
Paolo Carlini <[EMAIL PROTECTED]> writes:
> I have been waiting for > 15 minutes for 'jules' to unlock the library:
> how is this even possible? Are there operations taking *so* much time?
> Is there something I can do in such cases?
The process is now finished.
It was, I believe, a merge to csl
Paul Brook <[EMAIL PROTECTED]> writes:
> On Friday 20 May 2005 16:05, Paolo Carlini wrote:
> > Hi,
> >
> > I have been waiting for > 15 minutes for 'jules' to unlock the library:
> > how is this even possible? Are there operations taking *so* much time?
>
> Tagging a branch.
I don't think it was
"Joseph S. Myers" <[EMAIL PROTECTED]> writes:
> On Sun, 6 Mar 2005, Ian Lance Taylor wrote:
>
> > look at the ChangeLog for the appropriate year. This is also how some
> > other GNU programs organize their ChangeLog files, including libhava
> > and libs
Zack Weinberg <[EMAIL PROTECTED]> writes:
> Think about how machine_mode values are used. Almost the entire
> compiler is supposed to treat them as opaque things. You get them from
> e.g. int_mode_for_size; you may iterate over a class with
> GET_MODE_WIDER_MODE; you stash them in RTL and you pa
Phil Endecott <[EMAIL PROTECTED]> writes:
> I'm having trouble compiling code that uses the following macro from
> the Apache Portable Runtime:
>
> #define apr_atomic_cas(mem,with,cmp) \
> ({ apr_atomic_t prev; \
> asm volatile ("lock; cmpxchgl %1, %2" \
> : "=a" (prev
Mike Stump <[EMAIL PROTECTED]> writes:
> I did a checkin using ../ in one of the files and cvs screwed up.
> The ChangeLog file came out ok, but, all the others were created
> someplace else. I'm thinking those ,v files should just be rmed off
> the server... but, would rather someone else do th
Sanjiv Kumar Gupta <[EMAIL PROTECTED]> writes:
> I am using gcc 3.3.1 release as my port, and looks
> like I have hit a problem with greg.
You neglected to mention what target you are using.
> I couldn't understand why the insns 620 and 621 are
> being generated here as DI moves.
I'm not sure s
Diego Novillo <[EMAIL PROTECTED]> writes:
> This is happening in gcc.dg/tree-ssa/20040121-1.c. The test
> specifically tests that (p!=0) + (q!=0) should be computed as
> int:
>
> char *foo(char *p, char *q) {
> int x = (p !=0) + (q != 0);
> ...
> }
>
...
> When we call int_const_binop
N V Krishna <[EMAIL PROTECTED]> writes:
> I am trying to do some modifications to the register allocator and for the
> architecture I am dealing with, I want to handle different type of pseudos
> differently. All local scalars fall under one group, local struct/union
> variables under one group an
Sanjiv Kumar Gupta <[EMAIL PROTECTED]> writes:
> >>I couldn't understand why the insns 620 and 621 are
> >>being generated here as DI moves.
> > I'm not sure specifically why it got a DI move here, but it doesn't
> > look wrong. It's treating the struct named parts as DImode.
> >
> >>This is crea
Björn Haase <[EMAIL PROTECTED]> writes:
> Concerning 1.) Ian Lance Taylor has made a couple of suggestions on how to
> make the transition easier for the back-end maintainers. So it seems that
> there is already some activity around.
In fact Hans-Peter Nilsson is implementing
"Rasmussen, David Ravn" <[EMAIL PROTECTED]> writes:
> ***
> Information contained in this email message is intended only for use of the
> individual or entity named above. If the reader of this message is not the
> i
Mike Stump <[EMAIL PROTECTED]> writes:
> Forgive me ignorance, is there is use for the use of the label below?
>
> From rs6000, though, certainly there are other examples of this sort
> of thing in the md files:
>
> (define_insn ""
>[(set (pc)
> (match_operand:P 0 "register_operand
Steven Bosscher <[EMAIL PROTECTED]> writes:
> So you have a few instructions bundled into a VLIW instruction, and
> one of the instructions in the bundle is moved into the delay slot,
> thus breaking your VLIW bundle. Right?
I think there are two natural approaches.
1) Do the VLIW bundling afte
"Sung-Gu" <[EMAIL PROTECTED]> writes:
> I thought I might find a specfic directory in gcc sources whether it supports
> the files.
> I don't want to compile the whole source files. :(
gcc is just the compiler. Header files like byteswap.c and endian.c
are part of the system library. gcc does no
"Sung-Gu" <[EMAIL PROTECTED]> writes:
> I have another Linux machine.
> And I found the following messages:
>
>
> $cd /usr/include
>
> $ more endian.h
> /* Copyright (C) 1992, 1996, 1997, 2000 Free Software Foundation, Inc.
>This file is part of the GNU C Library.
Yes. gcc is not the GNU
Balaji S <[EMAIL PROTECTED]> writes:
> >>So you have a few instructions bundled into a VLIW instruction, and
> >>one of the instructions in the bundle is moved into the delay slot,
> >>thus breaking your VLIW bundle. Right?
> > I think there are two natural approaches.
> > 1) Do the VLIW bundling
Taoufik HNIA <[EMAIL PROTECTED]> writes:
> I am working on porting gcc for a 16 bits processor.
> I know that gcc supports arm,but I don't know if gcc supports 16 bits
> arm.So my question is :
> does gcc generate code for 16 bits arm ?
Yes, it does, with the -mthumb option.
This kind of questio
Rohit Agarwal <[EMAIL PROTECTED]> writes:
> As till now, I have been successful in making test programs run on the
> IXDP425 board compiled using a gcc compiler. Does that mean that I
> have ported eCos on the hardware? I know its a very silly question but
> since this is the first time I am worki
"Joseph S. Myers" <[EMAIL PROTECTED]> writes:
> Such tests are in general bugs. You'd have to ask Torbjorn about what the
> original purpose of the old parts of c-torture was, as that may have
> differed from the current GCC testsuite, but invalid tests should be
> removed (or, perhaps better,
Diego Novillo <[EMAIL PROTECTED]> writes:
> The problem is somewhat more widespread now with the tree
> optimizers. In particular with old test cases. Some of these
> cases are essentially optimized into empty functions by the time
> we get into the RTL passes.
Hmmm, yeah.
> We would have to a
In preparation for the future transition to subversion, I've written
some code to merge the old-gcc repository into current mainline. I
would like to see this merged repository used as the basis for the
conversion to subversion. The advantage is that it provides revision
history back to 1992, whe
Bharadwaj Yadavalli <[EMAIL PROTECTED]> writes:
> Can someone please point me to a place where I can get information
> about how gcc (2.96 and later) lays out class instances? In other
> words if I examine the contents of an object pointer, is there a
> document that specifies how the contents of
"Tabony, Charles" <[EMAIL PROTECTED]> writes:
> What does it mean by "unit none"?
First I'll note that you shouldn't see this when using the DFA
scheduler (define_insn_reservation, etc.). You should only see it
when using the old pipeline description (define_function_unit, etc.).
The old pipelin
Daniel Berlin <[EMAIL PROTECTED]> writes:
> > In other words, we're asked to agree that the type of an object
> > changes depending on how it is accessed.
> > For the benefit of readers, only the first sentence of this para is
> > the language of the standard; the rest isn't.
> >
> > That an ob
Richard Henderson <[EMAIL PROTECTED]> writes:
> I've got no interest in reading a thread with 250 messages wherein
> language lawyers battle it out in a no-holds-barred grudge match.
> Would someone like to summarize, preferably with a test case that
> one side assumes to be miscompiled?
As I rea
Kean Johnston <[EMAIL PROTECTED]> writes:
> What is the best way of including target-specific files in the
> version-specific gcc library directory? I need to include a
> file that will be referenced from LINK_SPEC as "gcc.map%s".
> IE, in the same place the startup files are located. So
> really
Vasanth <[EMAIL PROTECTED]> writes:
> What is the recommended way to do DW2 frame unwinding based exception
> handling for targets that do not support unaligned accesses in
> hardware? I did see the documentation about UNALIGNED_INT_ASM_OP, but
> not sure if that is meant to generate a directive t
Geoffrey Keating <[EMAIL PROTECTED]> writes:
> > const is inherently a characteristic of the object. It applies at
> > definition time. Casting away const in a reference does not change
> > the definition. Whether making an assignment through a pointer after
> > casting away const is legal depe
Geoff Keating <[EMAIL PROTECTED]> writes:
> This is part of what I meant by saying that your model isn't a match
> for the model in the standard. Your model had semantics attached to
> the access.
Despite evident appearances, I wasn't trying to make an argument from
the standard. I was trying t
"DC A" <[EMAIL PROTECTED]> writes:
> Hi! I'm completely new at gnu c and I 've a problem with getchar()
> method.
This mailing list is for the discussion of development of gcc. It is
not for C programming questions. Please find some other mailing
list. Thanks.
> My program is given below. fir
Mathieu Malaterre <[EMAIL PROTECTED]> writes:
> I have quite a surpising behavior with gcc when compiling the
> following code (*). Here is the output:
>
> $ g++ deprecated.cxx /tmp
> deprecated.cxx: In constructor `A::A(int)':
> deprecated.cxx:11: warn
Hanzac Chen <[EMAIL PROTECTED]> writes:
> Some idea: Maybe local stack use in the code compiled by GCC should be
> optimized 'cause some local variables are conditional. If the condition
> is not satisfied, then these variables don't need to be allocated from
> the stack (e.g. sub $VAR_SIZE, %esp)
Simon Tsai <[EMAIL PROTECTED]> writes:
> Where can I download gcc binary code for Linux? What's
> URL?
This is actually the wrong mailing list for this question. Can you
tell us why you wrote to this list, so that we can encourage people to
write to the correct list instead? Thanks. The right
"Ioannis E. Venetis" <[EMAIL PROTECTED]> writes:
> I downloaded gcc 4.0.1 and created the manual with 'make dvi'. While
> browsing through it, I noticed the option -ftree-dse, which is
> mentioned in paragraph 3.1 (Options summary) and in paragraph 3.10
> (Options That Control Optimization) under
Hi Jim, the documentation for -Wstrict-aliasing=2 says:
It warns about all code which might break the strict aliasing
rules that the compiler is using for optimization. This warning
catches all cases, but it will also give a warning for some
ambiguous cases that are safe.
However
"Paul C. Leopardi" <[EMAIL PROTECTED]> writes:
> Hi all,
> I did not receive a reply to my earlier message. Have I posted it to the
> wrong
> list? If so, what is the right list for this message?
> Thanks
>
> On Sat, 23 Jul 2005 07:23 pm, Paul C. Leopardi wrote:
> > How do I make the tests find
"Paul C. Leopardi" <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED]:~/src/gcc/gcc-4.0.1-obj> ../gcc-4.0.1/configure
> --prefix=/usr/local/gcc/gcc-4.0.1 --enable-threads=posix --disable-libgcj
> --with-system-zlib --enable-shared --enable-__cxa_atexit
> --enable-languages=c,c++ x86_64-suse-lin
"Paul C. Leopardi" <[EMAIL PROTECTED]> writes:
> The preamble to g++ testing says:
>
> make[1]: [check-gcc] Error 1 (ignored)
> (rootme=`${PWDCMD-pwd}`; export rootme; \
> srcdir=`cd ../../gcc-4.0.1/gcc; ${PWDCMD-pwd}` ; export srcdir ; \
> cd testsuite; \
> EXPECT=expect ; export EXPECT ; \
> if
"Paul C. Leopardi" <[EMAIL PROTECTED]> writes:
> I checked http://gcc.gnu.org/install/prerequisites.html
> Under "Tools/packages necessary for modifying GCC" it has
>
> autogen version 5.5.4 (or later)
>
> My fault, but... I'm just testing my bootstrap and am not intending to modify
> gcc, so
James E Wilson <[EMAIL PROTECTED]> writes:
> Ian Lance Taylor wrote:
> > -Wstrict-aliasing=2. It warns about more possible problems than
> > -Wstrict-aliasing, but it does not warn about all possible problems.
>
> This is the important point that I was trying to ge
"Ioannis E. Venetis" <[EMAIL PROTECTED]> writes:
> Sorry for the late response. Before creating the bug report I though I
> should search the bugs database and I found that a comment for bug
> 13756 mentions the missing documentation for -ftree-dse
> (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13
Kean Johnston <[EMAIL PROTECTED]> writes:
> I am getting weird warning messages from my assembler when
> gcov is being used. I have tracked what I think is the
> problem down but I don't really know how to fix it. The
> bit of assembler that causes the warning is:
>
> .type .LPBX0, @object
>
Kean Johnston <[EMAIL PROTECTED]> writes:
> > I don't understand why the .type and .size information is useless.
> Becuase its for a local lable only, not anything thats intended
> to wind up in the symbol table? I'm not sure what meaning a
> type and size has for a local lable like that?
Oh, I s
[EMAIL PROTECTED] writes:
> Does the instruction combiner regards (foo & 0xff) as a special case?
>
> I have two patterns which I expect to match all the
>
> if(foo & $(constant)) patterns. They are
>
> [(set (reg:CC_Z CC_REGNUM)
> (compare:CC_Z
> (and:SI (match_operand:
Chunjiang Li <[EMAIL PROTECTED]> writes:
> I wonder is it true that one Pseudo register is only corresponding to one
> basic block?
No, it isn't.
> the reg_info struct is:
>
> typedef struct reg_info_def
> { /* fields set by reg_scan */
> int first_uid;
Harald van Dijk <[EMAIL PROTECTED]> writes:
> I finally managed to track down the problem I've been having to this
> short code:
>
> typedef struct {
> unsigned car;
> unsigned cdr;
> } cons;
>
> void nconc (unsigned x, unsigned y) {
> unsigned *ptr
Diego Novillo <[EMAIL PROTECTED]> writes:
> On Tue, Aug 02, 2005 at 10:05:37AM -0400, Daniel Jacobowitz wrote:
>
> > Yes, it does - well, it's implementation defined, but GCC has long
> > chosen the natural interpretation. C99 6.3.2.3, paragraph 5. This is
> > no different from that classic exa
Andrew Pinski <[EMAIL PROTECTED]> writes:
> > Yes, this is a compiler bug in the expansion of memcpy, please file a
> > bug report. The solution is for the compiler to notice the memory
> > alignment of the destination and `do-the-right-thing' when it isn't
> > aligned.
>
> No it is not, o
<[EMAIL PROTECTED]> writes:
> > I'm wondering if I can get information from here on how to use the
> > binfo macros.
> >
> What are the binfo access functions for gcc 3.4.1? I'm having trouble
> creating the html files for gcc and I've been told BINFO_BASE_BINFO and
> BINFO_BASE_ITERATE, which I
Gunther Nikl <[EMAIL PROTECTED]> writes:
> I am trying to add instructions into function prologue/epilogue. These
> instructions shall save and load "fixed" registers to avoid assembly.
>
> Register saving in the prologue appears to work. The restore code in the
> epilogue aborts in flow.c/propag
Richard Henderson <[EMAIL PROTECTED]> writes:
> On Tue, Aug 02, 2005 at 01:45:01PM -0700, Ian Lance Taylor wrote:
> > Andrew Pinski <[EMAIL PROTECTED]> writes:
> >
> > > > Yes, this is a compiler bug in the expansion of memcpy, please file a
>
Gunther Nikl <[EMAIL PROTECTED]> writes:
> Is EPILOGUE_USES only for the save and restore? I would have to add
> some big chunk of code to it and that would propagate to several
> places. It seems emitting a USE has lower impact.
EPILOGUE_USES doesn't emit code. It simply takes a register
Mike Stump <[EMAIL PROTECTED]> writes:
> In general you'll want to understand how OSes allocate stack, and how
> the determine if an access is to the stack or not. The canonical
> unix way is to catch a fault, and if that fault is within X MB (8MB
> in years past) of the top of the stack, assume
"Balaji V. Iyer" <[EMAIL PROTECTED]> writes:
>I am adding a DFA scheduler for OpenRISC Processor in GCC. (I have not
> changed anything else). I don't see a difference in assembly at all. I
> would like to know how to make it recognize that there is a DFA
> scheduler.
Which sources are you wo
Sebastian Pop <[EMAIL PROTECTED]> writes:
> I'd like to ask GCC users in general: how many are using these params?
We use them at my current employer, mainly to remove limits which were
imposed to keep compile time under control. We have code which needs
to run as fast as possible, for which com
"Kaveh R. Ghazi" <[EMAIL PROTECTED]> writes:
[ Moved from gcc-patches to gcc ]
> At this point, I don't do any parsing of the "format-checking-data",
> this is where I would expect Ian's state machine language to appear.
To make this kind of thing useful, I see two paths that we can follow.
Th
Florian Weimer <[EMAIL PROTECTED]> writes:
> * Ian Lance Taylor:
>
> > I haven't tried to flesh this out any further. I'd be curious to hear
> > how people react to it.
>
> Can't we just use some inline function written in plain C to check the
>
Florian Weimer <[EMAIL PROTECTED]> writes:
> If I understand your %A/%B example correctly, it would look like this:
OK, I can see how that might work in a simple case. Now, can you give
me an example of matching %d with the various flags? In particular,
are you going to write a loop, and is gcc
"Giovanni Bajo" <[EMAIL PROTECTED]> writes:
> Florian Weimer <[EMAIL PROTECTED]> wrote:
>
> > Can't we just use some inline function written in plain C to check the
> > arguments and execute it at compile time using constant folding etc.?
>
>
> Do we have a sane way to (partially) execute optim
"Kaveh R. Ghazi" <[EMAIL PROTECTED]> writes:
> I strongly feel that the "inherit" command should not change the
> behavior of the inherited format depending on the --std= flag passed
> to GCC at compile time of the user's code. This change isn't right
> for users, their variable argument output r
Florian Weimer <[EMAIL PROTECTED]> writes:
> > Do we have a sane way to (partially) execute optimizers at -O0
> > without screwing up with the pass manager too much?
>
> Do we have to provide user-defined format string warnings at -O0?
Yes, we do.
(But, although I don't like this approach, I th
David Edelsohn <[EMAIL PROTECTED]> writes:
> I am pleased to announce that the GCC Steering Committee has
> appointed Ian Lance Taylor to the role of "middle-end" maintainer,
> joining Roger Sayle. The role covers all files that may get included
> into libbacken
Alan Modra <[EMAIL PROTECTED]> writes:
> It's a great pity that vfprintf doesn't return its va_list arg. If it
> did, you could chop the format string into pieces and have vprintf
> process the normal parts, consuming args as it goes.
You can do relatively limited parsing and still identify how
Tom Tromey <[EMAIL PROTECTED]> writes:
> Ian> The second approach is of course to write a little language which is
> Ian> powerful enough to describe printf. The state machine language I
> Ian> described earlier is too simple and perhaps overly cryptic.
>
> If we're doing that, why not use an al
On Aug 10, 2005, at 12:43 PM, Fariborz Jahanian wrote:
> + /* APPLE LOCAL begin radar 4153339 */
> + if (n_sets == 1 && GET_CODE (sets[i].src) == REG
> + && src_const && GET_CODE (src_const) == CONST_DOUBLE)
> + {
> + src_folded = src_const;
> + src_folded_cost =
Mark Mitchell <[EMAIL PROTECTED]> writes:
> My first comment is that we had a lot of bugs targeted at 4.1.0 that
> should never have been so targeted. Please remember that bugs that do
> not effect primary or secondary targets should not have a target
> milestone. There are several PRs that seem
Leehod Baruch <[EMAIL PROTECTED]> writes:
> Is it true that in a SET, a search for a _use_ of a register
> in the LHS should be done only inside a memory address?
See refers_to_regno_p for an example of a function which looks for
all uses of a register.
Ian
Benjamin Kosnik <[EMAIL PROTECTED]> writes:
> > Could we modify the CVS commit filters to *require* the right
> > versions? If it detects a commit with the wrong version (at least,
> > assuming the old rev had the right version), it can just reject it.
>
> Dunno if this is possible, but this wou
Mark Mitchell <[EMAIL PROTECTED]> writes:
> I've created a new 4.2 Project page for "response files", which is
> what Microsoft calls files that contain command-line options.
> Conventionally, if you pass "@file" as an argument to a program, the
> file is read, and the contents are treated as comm
Dale Johannesen <[EMAIL PROTECTED]> writes:
> The test of f->b comes out as
>
>testl $1048512, 73(%eax)
>
> This is wrong, because 4 bytes starting at 73 goes outside the
> original object and can
> cause a page fault. The change from referencing a word at offset 72
> to offset 73
> happen
Fariborz Jahanian <[EMAIL PROTECTED]> writes:
> Forgot to attach the patch:
>
> Index: i386.c
> ===
> RCS file: /cvs/gcc/gcc/gcc/config/i386/i386.c,v
> retrieving revision 1.795.4.33
> diff -c -p -r1.795.4.33 i386.c
> *** i386.c
Sergei Organov <[EMAIL PROTECTED]> writes:
> Laurent GUERBY <[EMAIL PROTECTED]> writes:
> > If we add a library function to handle this we might want to
> > add a GNU-style argument equivalent like
> >
> > gcc --arguments-from-file=file
>
> AFAIK gcc doesn't support any GNU-style arguments, isn'
Sergei Organov <[EMAIL PROTECTED]> writes:
> Anyway, my gcc docs only mention:
>
> --target-help
> --help
> --version
> --param NAME=VALUE
Yeah, it looks like the double dash long options got added without
ever being documented.
For the record, they were added here:
Sat Mar 6 15:08:59 1993 R
Kevin McBride <[EMAIL PROTECTED]> writes:
> If you look closely, you can see that %edi can be automatically loaded
> directly without problems, and that (%eax) can be directly loaded into
> (%esp). Is this behavior intentional (for bugs I don't know about in
> earlier processors) or could this op
Kevin McBride <[EMAIL PROTECTED]> writes:
> Please take notice that I am appealing my bug (number 23605) to the
> steering committee of GCC on the basis that it is a legimate
> bug/enhancement in need of a through research. I believe that Andrew
> Pinski is trying to keep the research from occuri
401 - 500 of 3176 matches
Mail list logo
