A lot of thanks for the pointer...
>Probably. Look for at pattern with "movsi" in the name.
In th document
http://gcc.gnu.org/onlinedocs/gccint/Insns.html#Insns
it is said that "An integer that says which pattern in the machine description
matches
this insn, or −1 if the matching has not yet b
Mark Mitchell <[EMAIL PROTECTED]> writes:
> We have a number of C++ PRs open around problems with code like this:
>
>struct S {
> void f();
> virtual void g();
>};
>
>typedef __attribute__((...)) struct S T;
>
> If the attribute makes any substantive change to S (e.g., cha
FX Coudert <[EMAIL PROTECTED]> writes:
> Hi all,
>
> For Fortran 2003 standard conformance, the Fortran front-end has to
> know at compile-time what integer mode corresponds to some C99 types,
> like intmax_t, intN_t, int_leastN_t, int_fastN_t.
>
> For intN_t and int_leastN_t, I can see how to g
[EMAIL PROTECTED] writes:
> I'll have a look to mips_secondary_reload_class, however now i don't get
> spilling/filling errors. I have a question: libgcc2.c is pretty stable, right?
> I mean i shouldn't looking for something going wrong with it.
Right, libgcc2.c is quite stable.
In a normal buil
Hi Ian
>
> > Can i disable filling/spilling for this register class?
>
> Sure: make the registers fixed.
>
> Or look at how the MIPS port handles HI and LO, with particular
> reference to mips_secondary_reload_class.
>
> Ian
what i'm trying to do is to code a backend for a "standard" DLX. Most th
Ian Lance Taylor wrote:
"Carlos O'Donell" <[EMAIL PROTECTED]> writes:
A relocated compiler should not look in $prefix.
I agree.
I can't approve your patches, though.
This patch is OK, once we reach Stage 1.
--
Mark Mitchell
CodeSourcery
[EMAIL PROTECTED]
(650) 331-3385 x713
[EMAIL PROTECTED]:/e/gcc/test_pg> ../gcc-4.1.1/config.guess
i686-pc-linux-gnu
[EMAIL PROTECTED]:/e/gcc/test_pg> /e/gcc4.1.1_install/usr/local/bin/gcc -v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../gcc-4.1.1/configure
Thread model: posix
gcc version 4.1.1
[EMAIL PROTECTED]
Benjamin Kosnik wrote:
For testing outside of the build directory, it would be convenient to
have $SUBJECT.
This could be used in conjunction with -dumpversion to create
on-the-fly include and library directory paths for C++ includes in a
sane manner, much like the following:
Why do you need
Hi all,
For Fortran 2003 standard conformance, the Fortran front-end has to
know at compile-time what integer mode corresponds to some C99 types,
like intmax_t, intN_t, int_leastN_t, int_fastN_t.
For intN_t and int_leastN_t, I can see how to get them by looking at
the width of the differe
"Carlos O'Donell" <[EMAIL PROTECTED]> writes:
> A relocated compiler should not look in $prefix.
I agree.
I can't approve your patches, though.
Ian
Joseph S. Myers wrote:
I was referring to the change in extend.texi
-the closing brace. It is ignored if the content of the structure, union
-or enumerated type is not defined in the specifier in which the
-attribute specifier list is used---that is, in usages such as
[EMAIL PROTECTED] __attrib
[EMAIL PROTECTED] writes:
> i'm in the process of coding a GCC backend for a certain RISC-like
> architecture.
> Its register architecture consists of an integer register file (32 regs) and
> two
> additional hard regs that should be programmer visible. Accesses to these hard
> regs are also emi
Steven Bosscher <[EMAIL PROTECTED]> writes:
> As far as I can tell, dwarf.h is not included anywhere in gcc/
> or any of its subdirectories. Is there any reason not to remove
> this file?
I think dwarf.h was orphaned when dwarfout.c was removed in 2003. I
think we should remove it.
Ian
My apologies for even bringing it up. It appears we'll most likely do
our own analysis.
Regards,
Greg
>The enclosed unclassified technical data / software is being
transmitted under License Exception "NLR" and is to be used solely by
the individual / organization to whom it
Jason Merrill wrote:
I don't think my patch changed the handling of class typedefs; certainly
my intent was only to change how we handle
class __attribute ((foo)) C
Previously we rejected it, now we apply the attributes to the class.
OK, that certainly makes sense. (That's one of the ite
On Mon, 16 Oct 2006, Jason Merrill wrote:
> Mark Mitchell wrote:
> > Yes, I would be happy to explicitly ignore semantic attributes in typedefs
> > as well, with a warning (or even an error). However, I had not realized
> > that we ever did that; I'm surprised that the change that instituted this
Thanks very much. I am planning to use this output to help me add some
debugging features to GDB, involving temporal logic, but the
optimizations involve using a CFG. The dream for my project would be
to add an option to GC to print the CFG data to a file, and then parse
it and do some analysis o
Mark Mitchell wrote:
Yes, I would be happy to explicitly ignore semantic attributes in
typedefs as well, with a warning (or even an error). However, I had not
realized that we ever did that; I'm surprised that the change that
instituted this is so recent. I suppose that explains why we're
su
> but in the meantime, I'm wondering if there is a much easier way to go
> about this that I'm currently overlooking.
...instead I will rip off comp_base_dir from libgloss.exp.
-benjamin
Call dump_flow_info() defined in cfg.c to output the pred and succ of
each block. You can use this output to construct the CFG.
Maybe the software graphviz can help you to visualize the CFG.
On 10/16/06, Rob Quill <[EMAIL PROTECTED]> wrote:
Hi,
Does anyone know if it is possible to view/acces
Hi,
Does anyone know if it is possible to view/access/print out the
control flow graphs produced by GCC, either at compilation time, or
after compilation has taken place?
Thanks for your time.
Rob
On Mon, Oct 16, 2006 at 05:20:44AM -0700, Mohamed Shafi wrote:
> hello all,
>
> Sorry i am asking this kind of question.This might be weird to most of you
> but i am new to GCC.
> Can somebody tell me how to analyze the below instruction pattern
>
> (insn 8 6 9 1 (parallel [
> (set (
(insn 8 6 9 1 (parallel [
(set (reg/f:SI 32)
(symbol_ref:SI ("t") ))
(clobber (reg:CC 21 cc))
]) -1 (nil)
(nil))
Here is an answer to your first question:
8 6 9 are the serial numbers of the current, previous and next instructions
in the instru
hello all,
Sorry i am asking this kind of question.This might be weird to most of you but
i am new to GCC.
Can somebody tell me how to analyze the below instruction pattern
(insn 8 6 9 1 (parallel [
(set (reg/f:SI 32)
(symbol_ref:SI ("t") ))
(clobber (reg:
Hi all,
I 'm making a shared object for ARM9 with -fprofile-arcs and
-ftest-coverage options.
GCC version 3.3.2
I 'm making the shared object with in 2 cases :
1) By doing an -fpic over the files to be included in the shared object.
2) By not doing an -fpic over the files to be included in the sh
Hi there
i'm in the process of coding a GCC backend for a certain RISC-like architecture.
Its register architecture consists of an integer register file (32 regs) and two
additional hard regs that should be programmer visible. Accesses to these hard
regs are also emitted related to certain RTL pat
For testing outside of the build directory, it would be convenient to
have $SUBJECT.
This could be used in conjunction with -dumpversion to create
on-the-fly include and library directory paths for C++ includes in a
sane manner, much like the following:
%g++ -print-install-prefix
/mnt/share/bld
Hello,
(I'm still a newbie in gcc)
I am interested in -fwhole-program analysis (flag_whole_program) and I know
that with -O3 -fwhole-program the cgraph_nodes is cleaned (in cgraphunit.c
probably by cgraph_varpool_remove_unreferenced_decls) so that only functions
callable from main are kept (as
28 matches
Mail list logo
