Jaka Močnik writes:
> in emit_library_call_value_1(), local var stack_usage_map_buf is
> allocated with
>
> stack_usage_map_buf = XNEWVEC (char, highest_outgoing_arg_in_use);
> stack_usage_map = stack_usage_map_buf;
>
> allocating a buffer with 1 char for each byte of stack required for
> out
Jaka Močnik writes:
> Dne 10.02.2009 (tor) ob 17:14 -0800 je Ian Lance Taylor zapisal(a):
>> I don't quite see it. highest_outgoing_args_in_use is at least as large
>> as args_size.constant, and that counts the locate.size for each
>> argument. So it should always
Janis Johnson writes:
> My question, though, is about the case of the letters in the suffixes.
> N1169 says "note that the suffix is case insensitive"; should I take
> that literally and allow any mix of cases (as GCC currently does), or
> require that the same case be used within a particular su
Paolo Bonzini writes:
>> That is in brief how I see it and there are a lot of reload details
>> missed (like virtual register eliminations or addressing displacement
>> constraints etc).
>
> I suppose those would stay in reload?
I see no reason for those to stay in reload (especially since I thi
"H.J. Lu" writes:
> It may be a known issue. Does gcc follow Section 5.1.6 Scope Encoding
> in C++ ABI:
>
> http://www.codesourcery.com/public/cxx-abi/abi.html#mangling
>
> I tried the example. But it won't compile. I changed it to:
>
> [...@gnu-6 tmp]$ cat x.cc
> namespace N {
> inline c
Anthony Newnam writes:
> Should I do something like a binary svn search between revisions
> 124707 and 132947? It takes such a long amount of time to compile g++,
> almost a half an hour with my quad core, that it didn't seem practical
> try to do build so many times. I guess there is probably a
"H.J. Lu" writes:
>>> "_ZZN1N1fEiEs": encoding of N::f::"Itanium C++ ABI" (no discriminator)
>>
>> The discriminator is optional and is up to the discretion of the
>> compiler. This doesn't matter for interoperability purposes, because
>> such names can not be referenced from other translation u
Daniel Jacobowitz writes:
> On Fri, Feb 13, 2009 at 12:00:38PM -0800, Ian Lance Taylor wrote:
>> > Another issue for scope encoding. C++ ABI:
>> >
>> > ---
>> > Occasionally entities in local scopes must be mangled too
>> > (e.g. because
"H.J. Lu" writes:
>> HJ, do you still see a problem here?
>>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12056
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39188
Fine, but those are different problems. And I'm not sure 12056 is a
real problem at all.
Ian
Jeff Law writes:
> Ian Lance Taylor wrote:
>>
>> I see no reason for those to stay in reload (especially since I think
>> reload should disappear entirely). It is reasonable to pick the total
>> maximum size of the stack frame, and thus resolve all displacement
>
Jeff Law writes:
>>> I would agree that careful relaxation of displacements is no longer as
>>> important as it once was, I don't think we can just hand wave away
>>> the displacement issues
>>>
>>> 1. The stack frames don't have to be that big to bump up against
>>> these problems.
>>>
>>> 2.
Jeff Law writes:
>> No, that makes no sense. What I'm suggesting is that we fix the stack
>> offsets of all local variables before register allocation, based on a
>> conservative assessment of how many registers will be saved on the
>> stack. Then we know during register allocation whether the
Bernd Schmidt writes:
> Ian Lance Taylor wrote:
>
>> No, that makes no sense. What I'm suggesting is that we fix the stack
>> offsets of all local variables before register allocation, based on a
>> conservative assessment of how many registers will be s
Jeff Law writes:
> Ian Lance Taylor wrote:
>> Jeff Law writes:
>>
>>
>>>> No, that makes no sense. What I'm suggesting is that we fix the stack
>>>> offsets of all local variables before register allocation, based on a
>>>> cons
Joern Rennecke writes:
>> By the way: Are there better places to ask such questions like in gcc-help?
>
> If you actually need a new gcc backend and want it to be done well. you
> should instruct an experienced contractor to do it for you, or hire an
> in-house expert.
>
> Your question reveals t
Patrick Moran writes:
> We are two students in a Compiler Design course who have been
> assigned to work on a gcc beginners project. We have chosen the
> project on making pseudo-templated containers, and we had some
> questions about the semantics you want from them. The gcc page
> specific
I've put a project proposal for split stacks on the wiki at
http://gcc.gnu.org/wiki/SplitStacks . The idea is to permit the stack
of a single thread to be split into discontiguous segments, thus
permitting many more threads to be active at one time without worrying
about stack overflow or about wa
Joel Sherrill writes:
> Ian Lance Taylor wrote:
>> I've put a project proposal for split stacks on the wiki at
>> http://gcc.gnu.org/wiki/SplitStacks . The idea is to permit the stack
>> of a single thread to be split into discontiguous segments, thus
>> pe
Andi Kleen writes:
> Ian Lance Taylor writes:
>
>> I've put a project proposal for split stacks on the wiki at
>> http://gcc.gnu.org/wiki/SplitStacks . The idea is to permit the stack
>> of a single thread to be split into discontiguous segments, thus
>>
Mathieu Lacage writes:
> On Thu, 2009-02-26 at 14:05 -0800, Ian Lance Taylor wrote:
>> I've put a project proposal for split stacks on the wiki at
>> http://gcc.gnu.org/wiki/SplitStacks . The idea is to permit the stack
>> of a single thread to be split into di
Mathieu Lacage writes:
> On Fri, 2009-02-27 at 08:54 -0800, Ian Lance Taylor wrote:
>
>> > It would be totally awesome to do this if you could provide an option to
>> > delegate to a user-provided function the allocation and deallocation of
>> > the stack bl
John Regehr writes:
> This effort is relevant:
>
> http://research.microsoft.com/en-us/um/people/jcondit/capriccio-sosp-2003.pdf
Yes. Unfortunately, their analysis which lets them avoid testing at the
entry to each function requires a complete call graph, which is not
something gcc can assume i
Jay Foad writes:
>From an optimisation pass's point of view, what's the difference between:
>
> 1. a PLUS expression that gives an undefined result on overflow, and
> 2. a PLUS expression with a guarantee that the result won't overflow.
>
> I can't see how they will be handled any differently in
Ben Elliston writes:
> On Sat, 2009-02-28 at 18:31 +0100, Eric Botcazou wrote:
>
>> * gcc-interface/Makefile.in (cygwin/mingw): Revert accidental
>> EH_MECHANISM change in r130816.
>
> I've seen a few ChangeLog entries like this of late, so thought I would
> raise something: is it now a
Takis Psarogiannakopoulos writes:
> On Sun, 1 Mar 2009, Mark Mitchell wrote:
>
>> >> I think there's some confusion here. There is no relationship between
>> >> the ASM_SPEC definition in a config *.h file regarding options to be
>> >> passed to the assembler and the old "asmspec" parameter to
>
Michael Veksler writes:
> In this case, how is it possible to copy the objects? Will things just
> crash at run-time?
Although people have been discussing copying the objects, I should point
out that my original proposal suggests not copying. Instead the code
can always access the objects via p
"Amker.Cheng" writes:
> if test "${gcc_cv_as+set}" = set; then
> :
> else
> #other commands...
> fi
Note that the other commands set gcc_cv_as.
> I don't know much about configure process, So where does gcc_cv_as come from?
The first time you run configure, it is not set, and the "other
c
"Bingfeng Mei" writes:
> #define A 255
>
> int tst1(short a, short b){
> if(a > (b - A))
> return 0;
> else
> return 1;
>
> }
>
>
> int tst2(short a, short b){
> short c = b - A;
> if(a > c)
> return 0;
> else
> return 1;
>
> }
These computations are different. As
Richard Guenther writes:
> I agree. Btw, for the addition case we generate
>
> leal(%rsi,%rdi), %eax
> xorl%eax, %esi
> xorl%eax, %edi
> testl %edi, %esi
> jns .L2
> .value 0x0b0f
> .L2:
> rep
> ret
>
> wh
Richard Earnshaw writes:
> On Fri, 2009-03-06 at 16:09 +0100, Paolo Bonzini wrote:
>> If this does not work, on ARM you can also hope for something like this:
>>
>> ADDR0, R1, R2
>> XORS R0, R2, R3
>> XORSMI R1, R2, R3
>> SWIMI #trap
>
> On ARM you can just check for o
I'm happy to report that the gcc-in-cxx branch can now bootstrap. That
is, the code in gcc proper can now be compiled with a C++ compiler.
My plan going forward is as follows (when we are back in stage 1):
* For each difference between trunk and gcc-in-cxx:
+ Try to implement a -Wc++-compat wa
"Kaveh R. GHAZI" writes:
> I'm curious whether there are any detectable differences in the resulting
> compiler when built with g++ rather than gcc. E.g. testsuite regressions,
> changes in the speed or size of cc1, etc. Also, is cc1 linked with
> libstdc++.so ? Stuff like that.
>
> Would you
Laurent GUERBY writes:
> On Fri, 2009-03-06 at 18:44 -0800, Ian Lance Taylor wrote:
>> I'm happy to report that the gcc-in-cxx branch can now bootstrap. That
>> is, the code in gcc proper can now be compiled with a C++ compiler.
>
> Hi, did you test with Ada enabled?
Philipp Marek writes:
> I already asked that on gcc-help@ but got no answer, so I'm trying again here.
Sorry, this is the wrong mailing list, and so is gcc-help.
gcc@gcc.gnu.org is for discussion of development of gcc. You are asking
a question about the assembler. The assembler is part of the
Ben Elliston writes:
>> I'm curious whether there are any detectable differences in the resulting
>> compiler when built with g++ rather than gcc. E.g. testsuite regressions,
>> changes in the speed or size of cc1, etc. Also, is cc1 linked with
>> libstdc++.so ? Stuff like that.
>
> Also, is t
Bernd Roesch writes:
> Hello Richard
>
> On 09.03.09, you wrote:
>
>>> I believe one should convince the middle end to emit libcall
>>> for __builtin_xxx when the target has no builtint support.
>>
>> It of course does.
>
> On what codeplace is the redefine do in GCC source ?
This is in optabs.
Andreas Schwab writes:
> Etienne Lorrain writes:
>
>> Well, do I have any chance to have the 'asm (" %c0 ": : "" );' and
>> 'asm (" %a0 ": : "" );' documented if I submit a bug report?
>
> Those are already documented (*note (gccint)Output Template::).
But they aren't documented in the user ma
p...@po.cwru.edu (Paul Jarc) writes:
> To find gcc's installation prefix, I've been using
> "gcc -print-search-dirs". That worked up until 4.3, but now gcc
> chases symlinks so it can print symlink-free paths. What I want is
> the installation path just as it was spelled in
> "./configure --pref
dhua026 dhua026 writes:
> but most importantly, it used the "callz" instruction:
> /tmp/ccshjbUO.s: Assembler messages:
> /tmp/ccshjbUO.s:41: Error: no such instruction: `callz __fixunss...@plt'
> /tmp/ccshjbUO.s:53: Error: no such instruction: `callz __fixunss...@plt'
> make[1]: *** [_fixsfdi.o]
writes:
> Is it a problem that is worth being put onto bugzilla or I just have to do
> some trickery to save the compiler from being smarter than it is?
I think this is worth being put into bugzilla.
Ian
Paolo Bonzini writes:
> This in turn means that the description given by SHIFT_COUNT_TRUNCATED
> must be exact. Right now !SHIFT_COUNT_TRUNCATED means "I don't know",
> I want it to mean "it is never truncated".
You need to do more work to make that happen, as SHIFT_COUNT_TRUNCATED
applies to b
Francesco Montorsi writes:
> I'm new to GCC project so let me know if this is the wrong place
> where I can ask such a question.
The mailing list gcc-h...@gcc.gnu.org would be a better place.
> I've found a bug in Gcc 4.3.3 (on machine "Linux ubuntu
> 2.6.28-9-generic #31-Ubuntu SMP Wed Mar
Eric Fisher writes:
> I'd like to get more helpful information from the final .S file, such
> as basic block info, so that I can draw a cfg graph through a script.
The basic block information and the CFG graph is not reliable at that
point in the compilation. Your patch will work reliably for s
"Ph. Marek" writes:
> Philipp Marek marek.priv.at> writes:
>> > gcc -S tmp.S for some reason prints to stdout, so gcc -S tmp.S > tmp.s
>> > is what you need
>> Thank you very much, I'll take a look.
> I tried very hard to achieve that; and one time it seemed to work, but I
> cannot
> make it wo
I'm pleased to report that GCC was once again accepted as a supported
project for Google's Summer of Code program. Summer of Code is a
program sponsored by Google in which students are paid to contribute to
open source projects. This will be GCC's fourth year of participation.
For more informatio
Daniel Berlin writes:
> Why hasn't the SC sent something to the FSF like:
>
> "We are grateful for your concern about the issues this licensing
> change and subsequent discussion has brought up. However, sadly, the
> amount of time it is taking to reach consensus on how/what to change
> has begu
Peter Leist writes:
> How can I interpret the stack frame of the current_function? That
> means, how can
> I tell what is stored at the location FP+xxx. If that is not (easily)
> possible, it would
> help if I can somehow determine the type of data stored at that
> location (i.g is that
> a refer
Jerry Quinn writes:
> I just tried to bootstrap the gcc-in-cxx branch, but it fails in stage
> 2. If I expand the macros, the code looks OK to me.
>
> Any suggestions on how to go about tracking this down (if someone else
> doesn't get there first)?
Tobias Schlüter saw the same thing; I don't kn
Jerry Quinn writes:
> 2009-03-21 Jerry Quinn
>
>* config/i386/i386.c (ix86_function_specific_save): Don't check
>range of enum values.
I still don't know why I don't see this, but this is OK for the
gcc-in-cxx branch.
Thanks.
Ian
Richard Guenther writes:
>> But anyway, is the official position of the FSF still "thou shall use
>> not C++"? That would mean GNU binutils is in violation with gold, no?
>
> Probably people were clever enough not to ask the FSF about this ;)
Correct: I certainly did not ask the FSF about gold,
NightStrike writes:
> On Mon, Mar 23, 2009 at 2:38 AM, Joe Buck wrote:
>> GCC uses are the ones developed in the egcs days. Remember the old
>> days when the location of the development tree and the snapshots was
>> a secret, and people were threatened with banning if they let it out?
>
> Are y
Joe Buck writes:
> On Sun, Mar 22, 2009 at 11:53:59PM -0700, NightStrike wrote:
>> On Mon, Mar 23, 2009 at 2:32 AM, Joe Buck wrote:
>> > one. RMS wanted to have gcc use machines administered by the FSF; we
>> > pushed back. gcc.gnu.org is sourceware.org. We did agree that we
>>
>> A little o
domi...@lps.ens.fr (Dominique Dhumieres) writes:
> Could someone at FSF, directly or through the SC, be kind enough to
> explain in plain English for non-native speakers why it was so urgent
> to disrupt the release process for a licence exception.
I don't think any of us know. You would have to
Eduardo Cruz writes:
> but in c_parser_attributes this is made in the beggining of the loop:
...
> and why does it require the token "(" ? aren't we inside the function
> parameters list?
No. At that point the parser is reading the function attributes. The
comments explain the syntax in deta
domi...@lps.ens.fr (Dominique Dhumieres) writes:
> > BOSTON, Massachusetts, USA -- Tuesday, January 27, 2009 -- Today the Free
> > ^
> > Software Foundation (FSF), together with the GCC Steering Committee and the
> >
Kasper Bonne writes:
> In my example the compiler should be able to figure out that the
> register is not available for output (because it is used as input in
> the following line), so if this behavior is not a bug, it should
> be. IMO.
This thread should really be on gcc-h...@gcc.gnu.org, not
g
daniel tian writes:
> I am porting gcc to a 32bit RISC chip, and I met a logical
> error with 16bit arithmetic operations in generating assemble code.
> the error is between two 16bit data movement(unsigned short).
> While like A = B, A, and B are all unsigned short type. B is a
> result
Eric Botcazou writes:
>> I need to add support for some custom attributes that I need to know during
>> operand matching. I have no problem adding the attributes, but I don't
>> know what to do so that I can access the information later. My function
>> that is called to handle the attribute loo
Dobes writes:
>>> See the SYMBOL_REF_FLAGS stuff in rtl.h and various examples in the
>>> back-ends.
>> Or, better, look for uses of lookup_attribute.
>>
>
> OK, I've now got it working for globals and static locals by tagging the rtl
> in "encode_section_info" and checking for that tag later.
Dobes writes:
> Could you clarify a little about how/where to use lookup_attribute?
Use it wherever it is you need to know whether a symbol has your
attribute (I don't know when you need the information). In RTL you can
normally find the VAR_DECL using MEM_EXPR or REG_EXPR.
Ian
daniel tian writes:
> But the question is how I make the gcc know to extend every smaller
> mode to SImode. Now I check the MIPS port, maybe I can find some clue.
Maybe PROMOTE_MODE.
Ian
Jack Howarth writes:
> Does anyone know why the gcc.gnu.org ftp site
> is no longer available?
FTP on gcc.gnu.org is up again. The outage was accidentally caused
while updating the machine. Thanks for reporting it.
Ian
DJ Delorie writes:
> So... can I/we move forward on this? Or will such a change be
> rejected?
>
> BTW, Since sending this I discovered that gcc treats these
> differently wrt TARGET_NARROW_VOLATILE_BITFIELD:
>
> volatile struct
> {
> unsigned int a:8;
> unsigned int b:24;
> } t1;
>
> volati
"Joern Rennecke" writes:
> On Wed, Apr 01, 2009 at 03:30:25PM +0200, Richard Guenther wrote:
>> On Wed, Apr 1, 2009 at 3:18 PM, Joern Rennecke wrote:
>> > Is that an April fool's joke?
>> >
>> > The new license allows Java, but it does not allow linking with
>> > code that has no dependency on t
"Vincent R." writes:
> Now the question is can we declare a function with an eh region and will it
> construct prologue and epilogue ?
The instructions are already in a function. Why do you need a separate
prologue and epilogue for them?
Maybe I am missing the point here. It seems to me that
"Vincent R." writes:
> Yes I think I don't explain things very clearly, so what is important to
> know is that the __except keyword
> can be passed instructions(case 1) or directly a function(case 2).
I see that but I don't see why it matters.
> in the case 1) ie if you declare something like
"Vincent R." writes:
>> gcc will do the right thing if you put statements in an exception
>> region.
>
> Hum how gcc can do that kind of things, is it some kind of voodoo ?
> __except is not implemented yet and is more than a language construct
> because it's an
> OS thing.
> So maybe I need to
Dave Korn writes:
> Really, it's all pretty much the same as DW2, except that rather than
> calling a raise exception function in libgcc, it begins with a real processor
> exception that then ends up routing into the unwinder. From there it's all
> fairly analagous.
It sounds like it is diffe
Kirill Kononenko writes:
> There have been mentioned a couple of ideas indeed. But I would not
> like to spend a lot of my precious time on telling my thoughts and
> suggestions, if the topic is already decided elsewhere. So I basically
> want asking question which exactly JITing support GCC need
"Vincent R." writes:
> Once again what I describe above is simplified because when seh is used,
> there is a mechanism
> called virtual unwiding that I didn't explained but that is the reason to
> store the prologue length.
It's worth noting that in gcc the "prologue length" is normally an
unde
Dave Korn writes:
> Ian Lance Taylor wrote:
>
>> First, an exception can occur while executing an instruction which
>> accesses memory or does a division (admittedly only within a __try
>> block). The raise exception call, on the other hand, can only occur
>>
Dave Korn writes:
> Ian Lance Taylor wrote:
>
>> No fundamental difficulty that I know of. Lots of tedious work for
>> every backend setting RTX_FRAME_RELATED_P and adding
>> REG_FRAME_RELATED_EXPR notes to the manually constructed epilogue insns.
>>
>> And,
f...@redhat.com (Frank Ch. Eigler) writes:
> Ian Lance Taylor wrote:
>
>> [...] Earlier Bradley Kuhn had indicated that this would be covered
>> in the updated FAQ, but I don't really see it there. I sent him a
>> separate message asking him to update it.
>
&g
Guilherme Puglia <1c3br...@gmail.com> writes:
> To solve my problem I wanna debug the C front end. I was trying to
> debug the gcc main function, toplev_main. Unfortunately, I can't
> insert a break point in this line.
>
> I saw the site http://gcc.gnu.org/wiki/DebuggingGCC and
> http://gcc.gnu.or
Guilherme Puglia <1c3br...@gmail.com> writes:
> I´m having some troubles again. I wanna convert a tree structure to
> c_declspecs structure.
>
> Anybody know how I could do that?
That seems like an odd transformation to want to make. There is nothing
in the compiler which does that today. You c
Hans-Peter Nilsson writes:
> On Fri, 3 Apr 2009, Ian Lance Taylor wrote:
>> gcc's -fasynchronous-unwind-tables option is
>> intended to support unwinding the stack at any precise instruction
>> boundary, which might be adequate for this purpose if the OS can handle
Eduardo Cruz writes:
> does the function lookup_name distinguish the identifier between
> different contexts?
I assume you mean the function in the C frontend, in c-decl.c. That
function looks up the name in the current scope, so, yes, it will return
different DECL nodes when appropriate.
Ian
John Engelhart writes:
> Objective-C defines 'c_common_get_alias_set' as its language specific
> alias set manager. c_common_get_alias_set() seems(?) to only
> implement C's strict aliasing rules, with no provisions for
> Objective-C's needs.
> Can anyone with a much better understanding of GCC
Arthur Schwarz writes:
> 1: Any thought to including column numbers with line numbers on
> ERROR messages? Looking at a diagnostic message for a complex
> statement without a column number has lead to making an
> incorrect assumption as to what in the line is faulty. A
> column nu
Arthur Schwarz writes:
> I didn't mean to volunteer. I'm retired and therefor am both
> unhireable and hove no free time. But if you really (really) want
> ... I'd be glad to contribute in any way that I can. Provide what you
> need that I can do, and a means to give you feedback and I'm yours.
John Engelhart writes:
> The easiest, and I think safest, course of action would be to add a
> line in c_common_get_alias_set similar to the one I suggested. That
> is, if it is a pointer to something that looks even remotely like an
> objective-c "object", then just assume that it can alias any
"Blower, Melanie" writes:
> I am an employee of Intel Corp. who will be making future
> contributions to gcc, binutils, gdb and glibc. I am writing to request
> copyright assignment forms, and other legal forms that are deemed
> necessary by FSF, which will enable me to contribute to gcc, binutil
"Kaveh R. GHAZI" writes:
> What I would like to see is that the extra_configure_flags for mpfr
> actually check whether gmp is being built in-tree before passing
> --with-gmp-build=foo to mpfr's configure. But I don't get how to do that.
> If the mpfr case could be fixed, I could then copy the m
Arthur Schwarz writes:
> # include
> # include
>
> using namespace std;
>
> ifstream x;
> ifstream& y = x;
>
> int main(int argc, char** argv) {
> y = x;
> return 0;
> }
>
> g++.3.4.4 output
> m1.cpp: In member function `std::basic_ios >&
> std::basic_ios >::operator=(const
> std::basic_
Arthur Schwarz writes:
> operator=() is private in ios_base. Using private inheritance of
> ios_base the program below fails in the constructor when '=' is used
> (but not during memory initialization). I don't understand why
> assignment is prohibited.
Perhaps I misunderstand your question, but
Arthur Schwarz writes:
> "Remember: When a base class' access specifier is private, public and
> protected members of the base become private members of the derived
> class. This means that they are still accessible by members of the
> derived class but cannot be accessed by parts of your program
"Kaveh R. GHAZI" writes:
> On Fri, 10 Apr 2009, Ian Lance Taylor wrote:
>
>> Add a new shell variable in configure.ac extra_mpfr_configure_args. Set
>> it to what you want to pass to the mpfr configure. Call
>> AC_SUBST(extra_mpfr_configure
Eli Zaretskii writes:
> 2009-04-14 Eli Zaretskii
>
> * configure.ac (setobjs, msdosdjgpp): Move a-priori setting of
> existing and required library functions to with_target_subdir
> section, so that the native build does detect them at configure
> time.
This is OK.
T
manjunatha srinivasan writes:
> Is GCC is supporting sigma design board processors? If so which SMP
> processor series is supported. If GCC doesn't support how to enable
> the support for sigma design boards in GCC sources.
This sort of question should be sent to gcc-h...@gcc.gnu.org, not to
g.
bing wang writes:
> We are encounter a problem with low version of GCC in Red Hat
> Enterprise Linux 4.
> our software pass the compile on Fedora 6 with GCC 4 ,but fail the
> compiling in Red Hat Enterprise Linux 4 with GCC 3.XX.
> I just download a gcc4-4.1.1-53.EL4 Source RPM from
> ht
"Vincent R." writes:
> When implementing seh for arm(arm-wince-pe) we have a weird assembler
> message when
> declaring ASM_DECLARE_FUNCTION_NAME. This macro calls the
> arm_seh_header_function and
> if we are trying to directly access a new field (has_seh) from cfun struct
> we
> get an assemble
Last week I committed a patch to check for enum comparisons which are
invalid in C++. Today I committed a patch to check for enum conversions
during function calls which are invalid in C++. These new warnings are
enabled by -Wc++-compat.
I have not fixed every gcc backend to compile without prod
Vlad, I noticed that the code in setup_cover_and_important_classes in
ira.c does #ifdef CONSTRAINT__LIMIT. However, CONSTRAINT__LIMIT is not
a preprocessor macro; it is an enum constant defined in the generated
file tm-preds.h. I think that the code within the #ifdef is either
unnecessary or is n
房陈 writes:
> I really want to how does gcc compile code like *(ptr base +
> offset), where ptr base is the initial address of a pointer variable
> and offset is any legal integer expression. There is a example here:
>
> int i = 1;
> int j = 1;
> int *buf = (int*)malloc(10 *sizeof(
Michael Hope writes:
> Hi there. I'm looking at porting GCC to a new architecture which has
> a quite small instruction set and I'm afraid I can't figure out how to
> represent unintended side effects on instructions.
>
> My current problem is accessing memory. Reading an aligned 32 bit
> word
Jayashree Ramani writes:
> Hello GCC Experts,
This message should have been sent to gcc-h...@gcc.gnu.org rather than
g...@gcc.gnu.org. Please send any followups to gcc-help.
>
> I am an engineer trying to run gcov for our unit tests. We have a couple
> of DLLs and a few static libraries.
Jean Christophe Beyler writes:
> I've been working on the Machine description of my target and was
> wondering if you could help me out here.
>
> I've been trying to force GCC out of it's habit of generating this code :
> (insn 28 8 10 2 glob.c:13 (set (reg:DI 9 r9)
> (mem/s:DI (symbol_re
Adayadil Thomas writes:
> I was wondering if gcc had a restricted version which would enable me
> to write programs
> with a subset of C language.
This question would be better directed to the gcc-h...@gcc.gnu.org
mailing list. Please take any followups to that mailing list.
No, gcc does not i
Arthur Schwarz writes:
> In the following code fragment:
>
> # include
> # include
> # include
>
> using namespace std;
> void CommandLine(int argc, char** argv);
> int main(int argc, char** argv) {
>CommandLine(argc, argv[]);
>ifstream x.open(argv[1], ios:in);
>ofstream y.open(arg
Jean Christophe Beyler writes:
> For the moment, no change, the expansion code is actually not used in
> this case because GCC only presents me with the load from a global
> during or after reload. Therefore, it's already done and he doesn't
> seem to want to change his ways. I haven't played wit
1401 - 1500 of 3176 matches
Mail list logo
