Frederic Riss writes:
> 136 is a pseudo. I have movdf and movsf patterns that accepts
> constants. I'm not sure what happens. Also, strictly speaking, the
> unrecognized pattern above is a SI move and not a floating point move,
> isn't it?
Yes, it is.
> I managed to get thinks going by constrai
Frederic Riss writes:
> I use nonimmediate_operand as a movsi destination predicate. I think
> this is pretty standard. But if I follow the code in
> recog.c:general_operand, I can see that it will reject (subreg (subreg
> ...)) which my initial pattern is. So yes, my movsi destination
> predicat
Frederic Riss writes:
> On 6 January 2011 17:02, Ian Lance Taylor wrote:
>> Oh yeah, you should never have a subreg of a subreg. That's a bug.
>> Where did that come from?
>
> Oh, that's interesting information! I have a splitter for movdf that
> must be the
Tony Poppleton writes:
> 1. My plan is to start testing bugs against the latest stable build
> (4.5.2), on an Intel x86-64 architecture (possibly also testing 32 bit
> bugs). My main focus will be on "missed-optimizations", although I
> will try and do others too. I have read the
> http://gcc.g
Tom de Vries writes:
> The following fix makes sure that the cached live info is invalidated:
> ...
> @@ -1865,6 +1880,7 @@ redundant_insn (rtx insn, rtx target, rt
> {
> /* Show that this insn will be used in the sequel. */
> INSN_FROM_TARGET_P (can
Gidi Nave writes:
> I have a question regarding Plus reload situation I ran into in my
> port (which was taken from branch 4.6):
>
> I got the following insn: Set d1 (plus r1 -96).
> d1 and r1 are 2 registers from different classes.
>
> The reload (which take place at: reload1.c , gen_reload(ou
Gidi Nave writes:
> On Tue, Jan 11, 2011 at 4:30 PM, Ian Lance Taylor wrote:
>> Gidi Nave writes:
>>
>>> I have a question regarding Plus reload situation I ran into in my
>>> port (which was taken from branch 4.6):
>>>
>>> I got the followin
Gidi Nave writes:
> On Tue, Jan 11, 2011 at 5:34 PM, Ian Lance Taylor wrote:
>
>> So why doesn't d1 = d1 + -96 match the last instruction there?
>>
> because it's:add d,d unsigned
> we don't have: add d,d signed
>
> and in this case we need:
Gidi Nave writes:
> On Tue, Jan 11, 2011 at 7:22 PM, Ian Lance Taylor wrote:
>> Gidi Nave writes:
>>
>>> On Tue, Jan 11, 2011 at 5:34 PM, Ian Lance Taylor wrote:
>>>
>>>> So why doesn't d1 = d1 + -96 match the last instruction there?
>&
Robert Millan writes:
> I'm not familiar with PT_GNU_STACK. Does a working
> _dl_make_stack_executable() in glibc [1] indicate it's supported?
>
> [1]
> http://svn.debian.org/viewsvn/glibc-bsd/trunk/glibc-ports/kfreebsd/dl-execstack.c?revision=1685&view=markup
PT_GNU_STACK is a program header
Bill Cox writes:
> $ gcc myprog.c -lgit://github/~waywardgeek/sonic=0.1
In Go we have a program goinstall which looks at import statements and
pulls in required libraries, where the libraries are named based on
where the sources live. A similar process could work in the C/C++
world, based o
Achilleas Margaritis writes:
> I have a idea for automatic generation of headers in a c++ program.
> Having to maintain headers is a very time consuming task, and I think
> we will all benefit from such a thing. The idea is the following:
>
> Each time the compiler finds the pragma
>
> #pragma au
Matt Redfearn writes:
> Output of objdump -stabs:
Use DWARF.
You're right, though, it looks like the debug generation routines think
that the parameter is passed in memory. Specifically, DECL_INCOMING_RTL
of the PARM_DECL is a MEM. You're going to need to find out why that
is.
Ian
Achilleas Margaritis writes:
> How much do you spend in maintaining headers? answers welcomed from
> other members as well.
In C++, I personally spend very little time doing what I would describe
as "maintaining headers." I write class definitions in .h files and
function implementations in .cc
Achilleas Margaritis writes:
> On Thu, Jan 13, 2011 at 9:53 PM, Ian Lance Taylor wrote:
>> Achilleas Margaritis writes:
>>
>>> How much do you spend in maintaining headers? answers welcomed from
>>> other members as well.
>>
>> In C++, I persona
majia gm writes:
> libjava/interpret.cc:1480
>
> gcc 4.4.0, 4.4.2 and 4.5.2 have the same problem.
What precisely are you trying to say?
If you are trying to say that this code will not compile if
DIRECT_THREADED is not defined, then I agree. It appears to have been
broken by this patch, which
e any changes to gcc, and fixes some cases
which are clearly bugs, I plan to commit this patch to binutils mainline
and to binutils 2.21 branch after a few days if I don't hear any
comments.
Ian
2011-01-18 Ian Lance Taylor
* plugin.cc (class Plugin_rescan): Define
Andrew Pinski writes:
> On Tue, Jan 18, 2011 at 5:02 PM, Jack Howarth
> wrote:
>> While doing bootstraps with...
>>
>> make -j 8 profiledbootstrap BOOT_CFLAGS="-g -O3"
>>
>> I noticed the absence of these flags being utilized in libdecnumber, libffi,
>> libgcc, etc.
>> This also appears to be
p...@po.cwru.edu (Paul Jarc) writes:
> Jack Howarth wrote:
>> make -j 8 profiledbootstrap BOOT_CFLAGS="-g -O3"
>>
>> I noticed the absence of these flags being utilized in libdecnumber,
>> libffi, libgcc, etc.
>
> On a related note, how can I pass *linker* flags for linking libgcc?
> I've passed
Richard Guenther writes:
> Nice. Can we on the GCC side somehow identify Gold versions
> that support this and avoid -pass-through handling in that case?
Sure. The LDPT_GOLD_VERSION tag, which lto-plugin currently ignores,
will return the version of gold. I can bump that version when I commit
"David Mathog" writes:
> Can somebody please explain the behavior of the following program
> to me?
This question is not appropriate for the gcc@gcc.gnu.org mailing list,
which is for the development of gcc itself. It would be appropriate on
gcc-h...@gcc.gnu.org. Please take any followups to g
Daniel Marjamäki writes:
> Do you have any opinion about adding a warning for:
>
> int f(char c)
> {
> return 10 * (c == 13) ? 1 : 2;
> }
>
> The multiplication has no effect. The function returns either 1 or 2.
>
> It would be interesting to know how a MELT script could look like for
> such
Daniel Marjamäki writes:
> 2011/1/24 Ian Lance Taylor :
>
>> The problem with warnings for this kind of code in C/C++ is that it
>> often arises in macro expansions.
>
> I see... so it won't be included in gcc. :-(
Actually, I think it could be included in gcc, pro
Ian Lance Taylor writes:
> 2011-01-18 Ian Lance Taylor
>
> * plugin.cc (class Plugin_rescan): Define new class.
> (Plugin_manager::claim_file): Set any_claimed_.
> (Plugin_manager::save_archive): New function.
> (Plugin_manager::save_input_gr
The -pass-through option existed to
pass static archives to the linker via the plugin; that is unnecessary
when the plugin researches static archives anyhow.
Ian
2011-01-24 Ian Lance Taylor
* version.cc (version_string): Bump to 1.11.
Index:
Kevin André writes:
> Is that ever going to be fixed? If a front end mangles its AST
> representation, then it cannot be used for static analysis.
>
> Even if the constant folding in the front end is necessary for
> checking semantics, you could still keep the original source in the
> AST and sim
Black Bit writes:
> Could someone tell me if the work described in this paper
> http://www.linuxsymposium.org/archives/GCC/Reprints-2006/namolaru-reprint.pdf was
> completed and is part of gcc?Thanks
To the best of my knowledge the work has not yet beco
Richard Guenther writes:
> Sure, as it is non-invasive trying it is ok. I just wanted to see if it
> fixes any existing problem - it does not seem to (apart from
> maybe e-mail is so hard, a minor problem compared to
> programming GCC is so hard ;))
It does fix an existing problem, which is tha
David Daney writes:
> In trying to build libgo on mips64-linux we try to build all three
> multilibs (o32, n32 and n64 ABIs)
>
> For the n32 ABI, the configure script generates syscall_arch.go:
> ---
> package syscall
> const ARCH = "mips64"
> const OS = "linux"
> ---
>
> The Make
Rainer Orth writes:
> Ian Lance Taylor writes:
>
>> I guess ARCH == mips64 is going to be appropriate for any 64-bit MIPS
>> target. If you need a different syscall_linux_${GOARCH} file for
>> different mips64 targets, then I think we're going to need to test
David Daney writes:
> That's right, but for the sake of argument I would say that o64 is
> unimportant as it is not supported by the Linux kernel.
It's unimportant but I'd like to make sure the scheme leaves room for
it.
>> It again comes down to what GOARCH is supposed to mean: an ABI, or what
Ralf Corsepius writes:
> On 01/27/2011 07:15 PM, Joel Sherrill wrote:
>
>> What is the preferred combination of
>> --enable-newlib and --with-newlib settings
>> to build with newlib in the gcc source tree
>> but not build it and use the installed copy
>> for the Ada and Go builds?
>
> Theoretical
Andreas Schwab writes:
> Ralf Corsepius writes:
>
>> - Remove newlib from the source tree
>
> --without-newlib should probably be enough.
But that seems strange to me as some of the configure scripts test for
--with-newlib and adjust their configury accordingly. This would put
them in a positi
Basile Starynkevitch writes:
> I am not sure to understand what is the social rules to modify that. I
> suppose that any patch to that page should be approved with the same
> strong process as patches to trunk code?
I would say that any gcc maintainer may update the changes file without
explicit
Jean-Marc Saffroy writes:
> error: insn does not satisfy its constraints:
> (insn 1424 1423 141 (set (reg:DI 2 r2)
> (plus:DI (reg:DI 2 r2)
> (const_int 40 [0x28])))
> /home/jmsaffroy/cygnus/src/newlib/libc/time/strptime.c:165 24 {adddi3}
> (expr_list:REG_EQUIV (plus:DI (
Kenneth Zadeck <[EMAIL PROTECTED]> writes:
> Bootstrapped and regression tested against the version with zdenek's
> original code (since this directly tickled the failure and
> bootstrapped (and in the process of regression testing) against the
> current mainline. Both on i686-pc-linux-gnu.
>
> K
Eric Fisher <[EMAIL PROTECTED]> writes:
> I guess that the macro NGARDS is relevant to the guard digit. But I
> still failed to have a clear conception about what it means. Others
> are easy to know by IEEE 754 and "What Every Computer Scientist Should
> Know about Floating-Point Arithmetic". Exce
Steven Bosscher <[EMAIL PROTECTED]> writes:
> The proposed work-around is to avoid confusing RTL alias analysis by
> simply not presenting it with situations where two references to the
> same memory can have different alias sets.
To recapitulate.
RTL alias analysis assumes that you can reorder
"John David Anglin" <[EMAIL PROTECTED]> writes:
> > No, the ISO C standard is clear that the value of an uninitialized
> > variable is indeterminate. It may be a trap representation, or it may
> > be an unspecified value. In the latter case it must have the correct
> > type. But there is no oth
[EMAIL PROTECTED] (Kai Henningsen) writes:
> ian@airs.com (Ian Lance Taylor) wrote on 20.01.06 in <[EMAIL PROTECTED]>:
>
> > When dealing with unions, you can take pointers to different fields in
> > the unions. If the fields have different types, these pointers can
"Dave Korn" <[EMAIL PROTECTED]> writes:
> I think he's saying that _this_ one might generate invalid code:
>
> void test(void)
> {
> union { int i; double d; } u;
> int *ip;
> double *dp;
> int ii;
> double dd;
>
> dp = &u.d;
> ip = &u.i;
Richard Sandiford <[EMAIL PROTECTED]> writes:
> I was just trying to point out that Ian's claim that the original code
> was valid doesn't reflect what GCC implements.
Yeah, I think I'm going to step back from trying to argue what is and
is not valid. To cut to the chase, I think the best approa
Zdenek Dvorak <[EMAIL PROTECTED]> writes:
> OK to revert this workaround now? Mainline now passes bootstrap &
> regtesting on i686 without it.
>
> Zdenek
>
> * loop-iv.c (iv_analysis_loop_init): Use df analysis in a more
> efficient way.
This is OK.
Thanks.
Ian
"Lucas \(a.k.a T-Bird or bsdfan3\)" <[EMAIL PROTECTED]> writes:
> 1) What would need to be done to reg-stack.c to allow other ports
> besides i386 to use it? (support for multiple-stack machines would be
> REALLY nice, but rather far off) (any other ideas?)
reg-stack.c is pretty closed tied to
Bernd Schmidt <[EMAIL PROTECTED]> writes:
> Let me ask a really stupid question. Where are we supposed to be
> clearing BB_DIRTY flags?
>
> I instrumented the old version of the struct-equiv patches to give me
> some information about the basic blocks it's being called for, and
> noticed that bl
Peter Steinmetz <[EMAIL PROTECTED]> writes:
> Currently, within the ready_sort macro in haifa-sched.c, the call to qsort
> is passed "rank_for_schedule" to help it decide which of two instructions
> should be placed further towards the front of the ready list.
> Rank_for_schedule uses a set of ord
DJ Delorie <[EMAIL PROTECTED]> writes:
> I'm looking at an insn that has these reloads [attached]. Note that
> reload2 is not needed IF the reload 1 gets resolved. I haven't
> figured out yet how to tell gcc this. Suggestions? The fb+0
> construct is something I create to recognize patterns th
Denis Chertykov <[EMAIL PROTECTED]> writes:
> Code fragment from reload1.c: reload()
>
> if (caller_save_needed)
> setup_save_areas ();
>
> /* If we allocated another stack slot, redo elimination bookkeeping. */
> if (s
Perry Smith <[EMAIL PROTECTED]> writes:
> How do I keep track of the "LTO" design process? I may not be able
> to help 'cause I don't know enough about gcc's internals but I'd like
> to if possible.
You read the mailing list [EMAIL PROTECTED] So you're already doing
the right thing.
Ian
Denis Chertykov <[EMAIL PROTECTED]> writes:
> > > I think that better to call update_eliminables() somewhere after
> > > setup_save_areas()
> >
> > Exactly. We do that. About 15 lines after the lines you quoted
> > above.
> >
> > What am I missing?
>
> I'm (exactly AVR port) need in call to u
"Eric Fisher" <[EMAIL PROTECTED]> writes:
> While I read the mips.md, I find there are some constraints used in
> function call templates, such as 'c' and 'j'. But these two
> constraints seem not be defined and I can't find their explanation
> both in source files and gcc internal. Well, aren't t
Marcin Dalecki <[EMAIL PROTECTED]> writes:
> Looking at the regor.c code I came across the function
> try_merge_delay_insns().
> There around the line 1488 we will find the following code:
>
> merged_insns = gen_rtx_INSN_LIST (SImode, dtrial,
>
Marcin Dalecki <[EMAIL PROTECTED]> writes:
> > An INSN_LIST which goes into the REG_NOTES field must use a register
> > note such as REG_DEP_TRUE in the mode field. But merged_insns does
> > not go into the REG_NOTES field. It is only used within the function
> > try_merge_delay_insns. Look at
Currently, when we see code that compares a bitfield to a constant, in
some cases we will turn the bitfield from a COMPONENT_REF into a
BIT_FIELD_REF. For example, this test case is based on PR 22563:
struct s
{
int a : 3;
};
struct s g;
int
foo ()
{
g.a = 2;
return g.a != 2;
}
In .003t.
"Eric Fisher" <[EMAIL PROTECTED]> writes:
> I installed cross gcc3.4.4 on my linux/pc server with
> --target=mips-elf. When I use mips-linux-gcc to compile a c file, the
> assembly code will have psuedo-op used for system v.4 (e.g. .cpload).
> And the object file is of big endian. So I have to use
"Eric Fisher" <[EMAIL PROTECTED]> writes:
> I think we shouldn't make abicalls as default in my opinion. :-)
Since all code that runs on MIPS GNU/Linux and uses shared libraries
must be compiled with abicalls, it would be rather unfortunate if
abicalls were not the default for the mips-linux-gnu
Daniel Towner <[EMAIL PROTECTED]> writes:
> I maintain a port of gcc for an embedded processor which has a HALT
> instruction. This instruction stops the processor, and generates an
> appropriate interrupt to indicate to its parent system that it has
> stopped. The instruction is accessed by the p
Mark Mitchell <[EMAIL PROTECTED]> writes:
> The new pex-win32.c code doesn't operate correctly when used for
> MinGW-hosted tools invoked from a Cygwin window. In particular, process
> creation ("gcc" invoking "as", say) results in a DOS console window
> popping up. When invoked from a DOS windo
When I compile the attached test case with mainline, I get this:
foo.cc: In function ‘void foo(const B&)’:
foo.cc:3: error: ‘B::B(const B&)’ is private
foo.cc:13: error: within this context
I don't understand why, as I don't see the copy constructor being used
anywhere. It seems to me this code
David Fang <[EMAIL PROTECTED]> writes:
> The relevant text appears in gcc-3.4's release notes:
> "When binding an rvalue of class type to a reference, the copy constructor
> of the class must be accessible."
Thanks. I see that I have managed to ask about a "frequently reported
bug." Sorry about
Paolo Bonzini <[EMAIL PROTECTED]> writes:
> >> The lower-subreg patch that Richard Henderson posted, and that
> >> comes up again and again from time to time, may also help. It does
> >> require a bit of hacking in the MDs (mostly removing the DImode
> >> patterns for logical operations since the
"Ling-hua Tseng" <[EMAIL PROTECTED]> writes:
> Because I need to use the feature of `length' attribute (i.e., use
> get_attr_length() in machine description),
> I have to insert NOPs explicitly before performing the pass 58
> (shorten) such that the shorten pass can calculate the length of insns
Rask Ingemann Lambertsen <[EMAIL PROTECTED]> writes:
> (insn 12 14 13 0 (parallel [
> (set (subreg:SI (reg:DI 61) 0)
> (xor:SI (subreg:SI (reg/v:DI 59 [ a ]) 0)
> (subreg:SI (reg/v:DI 60 [ b ]) 0)))
> (clobber (reg:CC 17 flags))
>
Google is hosting Summer of Code again this year. This is a program
in which they sponsor students to work on open source projects. The
students work under the guidance of mentors on specific approved
projects. For each completed project, Google will pay the student
$4500 and the project $500.
Andrew Haley <[EMAIL PROTECTED]> writes:
> Converting a vector of floats (via a cast) to a vector of ints of the
> same size uses a VIEW_CONVERT_EXPR, so the data are simply copied, not
> converted. This is different from a cast from scalar float to int,
> where a conversion is performed.
In gen
Paul Brook <[EMAIL PROTECTED]> writes:
> > In general there is a conflict within gcc between treating vectors as
> > unitary types and treating them as collections. In this case we are
> > treating them as unary. However, I think that by analogy to the way
> > we handle arithmetic, and given the
I threw together a simple project page on the Wiki for people looking
for Summer Of Code proposals:
http://gcc.gnu.org/wiki/SummerOfCode
If anybody has any other suggestions, please feel free to add them to
that page.
Thanks!
Ian
iticism) are welcome.
> Also, if someone wants to participate as a mentor for this project
> [*], please get in contact with Ian Lance Taylor
> and me.
This looks like a good plan to me, well described, well thought out,
and doable. Please submit it to Summer of Code when they start taking
Martin Reinecke <[EMAIL PROTECTED]> writes:
> I'm trying to learn about GCC's support for vector arithmetic and found
> the section "Using vector instructions through built-in functions", which
> answers a lot of questions, but unfortunately does not address things
> like gathering scalar values i
DJ Delorie <[EMAIL PROTECTED]> writes:
> For mips-elf builds, crtbegin.o is built with -G 0 ("in case $gp isn't
> used"). This makes __dso_handle be put in .data. However, the
> "prototype" created by cp/decl.c is "void *__dso_data" which causes
> GPrel addressing if your application is built wi
DJ Delorie <[EMAIL PROTECTED]> writes:
> In default_secondary_reload, we have this code:
>
> if (reg_class_subset_p (reload_class, insn_class))
> {
> gcc_assert (scratch_class == class);
> class = NO_REGS;
>
> Why doesn't it allow the scratch class to be
DJ Delorie <[EMAIL PROTECTED]> writes:
> > What reason is there to have scratch_class be something else?
>
> SECONDARY_RELOAD_CLASS has the option of limiting the reload class.
> The mn10300 has a generic SImode reload_in that allows GENERAL_REGS,
> but SECONDARY_RELOAD_CLASS specifies a smaller
Steve Ellcey <[EMAIL PROTECTED]> writes:
> By removing the AM_PROG_INSTALL definition from aclocal.m4 I was able to
> run autoconf 2.59 on the src tree intl subdir with no problems but I was
> wondering if we should take the time to synchronize the GCC intl
> directory with the src tree intl direc
[EMAIL PROTECTED] writes:
> I guess everybody is very busy. However, it would be nice to set up a
> page in the GCC Wiki with the list of projects accepted for this year
> SoC and some links. If someone has this information, I would volunteer
> to "wikify" it.
I've been assuming that Google was g
l Berlin
Andrew John Hughes Mark Wielaard
Phillip Jordan Benjamin Kosnik
Manuel López-Ibáñez Ian Lance Taylor
(Daniel is also mentoring four other applications for other
organizations. Good thing he's so effective.)
Ian
[EMAIL PROTECTED] writes:
> I'm a Msc. student in the computer science department of the Technion, the
> Israeli Institute of Technology.
> My thesis is on compile time checking of dynamic SQL queries using C++
> templates.
> There is a __COUNTER__ macro, supported by Microsoft C++ compiler which
"kernel coder" <[EMAIL PROTECTED]> writes:
This is all just boilerplate which is put at the end of every function
during RTL expansion.
> (insn 15 11 16 (nil) (clobber (reg/i:SI 2 v0)) -1 (nil)
>(nil))
Clobber the hard return register.
> (insn 16 15 13 (nil) (clobber (reg:SI 181)) -1 (nil)
[EMAIL PROTECTED] writes:
> void longcpy(long* _dst, long* _src, unsigned _numwords)
> {
> asm volatile (
> "cld \n\t"
> "rep \n\t"
> "movsl \n\t"
> // Outputs
> :
> // Inputs
> : "S" (_src), "D" (_dst), "c" (_numwords)
Benjamin Redelings <[EMAIL PROTECTED]> writes:
> substitution.o:(.data+0x0): multiple definition of
> `_ZN5boost7numeric5ublas21scalar_divides_assignIT_T0_E8computedE'
I can't make sense of that as a mangled name. It has template
parameter references but no template definition. That suggests th
"yang xiaoxin" <[EMAIL PROTECTED]> writes:
> Building project store
> =
> /usr/src/rpm/BUILD/OOB680_m5/store/source
> -
> /usr/src/rpm/BUILD/OOB680_m5/store/util
> --
> Making: ../unxlngi6.pro/lib/libstore.so.3
> g++ -Wl,-z,combreloc -Wl,-z,defs
Daniel Berlin <[EMAIL PROTECTED]> writes:
> It can also tell you who to copy on a ping email to make sure it
> actually goes to a maintainer.
> the interface is under construction, but "okay" for casual use.
> http://www.dberlin.org/patches/patches/maintainer_list/745 would be the
> one for this p
Daniel Berlin <[EMAIL PROTECTED]> writes:
> >> It can also tell you who to copy on a ping email to make sure it
> >> actually goes to a maintainer.
> >> the interface is under construction, but "okay" for casual use.
> >> http://www.dberlin.org/patches/patches/maintainer_list/745 would be the
> >>
Diego Novillo <[EMAIL PROTECTED]> writes:
> Daniel Berlin wrote on 06/13/06 23:24:
>
> > Does anyone believe this would help make sure patches stop dropping
> > through the cracks?
> >
> Not really. Technical solutions to social problems rarely work. Patch
> review is mostly a social problem.
Joe Buck <[EMAIL PROTECTED]> writes:
> The SC mainly has negative power, it can't make people do work.
> There have been a number of proposals that basically amount to threatening
> the patch reviewers with negative consequences, but I'm not for that.
> Certainly we can talk about mechanisms to he
Gabriel Dos Reis <[EMAIL PROTECTED]> writes:
> while looking into a recent mismatch between GCC-4.x and a C dialect
> EH implemented as setjmp/longjmp, I recalled there was a talk about
> extending GNU C with __try/__finally construct:
>
> http://gcc.gnu.org/ml/gcc-patches/2002-11/msg00239.
Atsushi Nemoto <[EMAIL PROTECTED]> writes:
> If I compile this code with gcc 4.1.1 (-O2),
>
> extern __thread int x;
> int foo(int arg)
> {
> if (arg)
> return x;
> return 0;
> }
>
> I got this output.
>
> foo:
> .frame $sp,0,$31 # vars= 0, regs= 0
"kernel coder" <[EMAIL PROTECTED]> writes:
> But when i issued the make all-gcc command .Following error occured
>
> ../../gcc-4.1.0/gcc/config/ABC/ABC.md: unknown mode `V2SF'
>
> Would u please explain why this error is being generated.Also a bit of
> explaination of 'V2SF' mode will helpful.
"kernel coder" <[EMAIL PROTECTED]> writes:
> > V2SF will be created by the line
> > VECTOR_MODES (FLOAT, 8);
>
> Yes you are absolutely right.When i changed the name of file
> ABC-modes.def to 1ABC-modes.def ,i got the following error
>
> make[1]: *** No rule to make target
> `../../gcc-4.1.
Daniel Jacobowitz <[EMAIL PROTECTED]> writes:
> On Fri, Jun 16, 2006 at 02:12:29PM -0700, Ian Lance Taylor wrote:
> > The computation of the address of x was moved outside the
> > conditional--that is, both the rdhwr and the addu moved. You'll have
> > to fig
"kernel coder" <[EMAIL PROTECTED]> writes:
> > ../../gcc-4.1.0/gcc/config/ABC/ABC.md:228: unknown value
> > `' for `mode' attribute
> > ../../gcc-4.1.0/gcc/config/ABC/ABC.md:228: unknown value
> > `' for `mode' attribute
>
> Sorry,these errors were just my mistake.I mistakenly comminted out the
>
Atsushi Nemoto <[EMAIL PROTECTED]> writes:
> On 19 Jun 2006 16:45:43 -0700, Ian Lance Taylor <[EMAIL PROTECTED]> wrote:
> > I tried recreating this, but I couldn't. I get this:
> ...
> > This of course is not ideal, since it unconditionally executes the
> &
Gyle Yearsley <[EMAIL PROTECTED]> writes:
> Hi my name is Gyle Yearsley. I am a design engineer at ZiLOG. We are in the
> process of releasing a new CPU. I have generated a gcc backend for this
> processor. I have read your contributions page and was wondering what the
> steps are and how to get p
Andrew MacLeod <[EMAIL PROTECTED]> writes:
> This describes my current work-in-progress, RABLET, which stands for
> RABLE-Themes, and conveniently implies something smaller.
Thanks for this proposal.
> ssa-to-rtl
> spill cost analysis
> global allocation
> spiller
> spill location optimizer
> i
Mark Mitchell <[EMAIL PROTECTED]> writes:
> Jason Merrill wrote:
> > Now, templates:
> >
> > template __attribute((visibility ("hidden")) T f(T);
> > #pragma GCC visibility push(default)
> > extern template int f(int);
> > #pragma GCC visibility pop
> >
> > This could really go either wa
Andrew MacLeod <[EMAIL PROTECTED]> writes:
> On Fri, 2006-06-23 at 15:07 -0700, Ian Lance Taylor wrote:
>
> > You omitted the RTL loop optimizer passes, which still do quite a bit
> > of work despite the tree-ssa loop passes. Also if-conversion and some
> > mino
"Roland Persson" <[EMAIL PROTECTED]> writes:
> For example, I have an add instruction that can add a 32-bit integer (with
> or without sign extension) to a 64-bit operand and store the result as 64
> bits.
>
> C code like:
> __int64_t a = 1;
> int b = 2;
> a += b;
>
> will generate code that sig
"Shaun Jackman" <[EMAIL PROTECTED]> writes:
> I'm using MULTILIB_OPTIONS and MULTILIB_DIRNAMES to compile a PIC/XIP
> toolchain. I'm familiar with the MULTILIB_EXCEPTIONS mechanism to
> specify incompatible configurations. How, though, do I indicate that
> msingle-pic-base depends on fPIC?
>
> MU
"H. J. Lu" <[EMAIL PROTECTED]> writes:
> There are
>
> ix86_init_mmx_sse_builtins ()
> {
> ..
> /* The __float80 type. */
> if (TYPE_MODE (long_double_type_node) == XFmode)
> (*lang_hooks.types.register_builtin_type) (long_double_type_node,
>
"Shaun Jackman" <[EMAIL PROTECTED]> writes:
> On 26 Jun 2006 14:04:36 -0700, Ian Lance Taylor <[EMAIL PROTECTED]> >
> The usual hacked up way is to MULTILIB_EXCEPTIONS to remove
> > -msingle-pic-base without -fPIC. Something like
> >
> > MULTILI
"Shaun Jackman" <[EMAIL PROTECTED]> writes:
> Reading through gcc/genmultilib, it looks as though
> MULTILIB_EXCLUSIONS can take a '!' parameter, but MULTILIB_EXCEPTIONS
> cannot.
I forgot about MULTILIB_EXCLUSIONS (it might be nice if it were
documented). I don't know if it would help you, sinc
2101 - 2200 of 3176 matches
Mail list logo
