Hello H.J.!
The testscase gcc.target/i386/sse2-vec-5.c you ported from mainline
fails on gcc-4.2 branch because __builtin_ia32_vec_ext_v16qi builtin
does not exist in gcc-4.2. This builtin corresponds to pextrb insn
that was introduced in SSE4 (gcc-4.3).
Also, the definition of __builtin_ia32_v
On Jun 20, 2007, at 9:40 PM, Pompapathi V Gadad wrote:
Hello Eric,
The target I am working on is 16-bit target and cannot support 64-
bit data types (DI mode).
How about conditionally declare the function?
#if LONG_LONG_TYPE_SIZE > 32
extern DItype __bswapdi2 (DItype);
#endif
You'll want t
Hello Eric,
bswapdi2 is implemented in libgcc2.c as follows:
#ifdef L_bswapdi2
DItype
__bswapdi2 (DItype u)
{
...
}
#endif
One way to avoid compilation of this function is to add condition macros
like: #if LONG_LONG_TYPE_SIZE > 32
However, libgcc2.h does not have such facility and declaration
Hi,
On Wed, 20 Jun 2007, I wrote:
> Index: gcc/df-problems.c
> ===
> --- gcc/df-problems.c (revision 125811)
> +++ gcc/df-problems.c (working copy)
> @@ -1574,7 +1574,7 @@
>/* Call-clobbered registers die across exception and cal
Hello. i am Alberto
I work with Gcc trees to modify c++ original code and dont find and i
need documentation about trees because the web isnt enought information.
Where are docs about gcc trees and macros to access it?
Thanks you
Alberto
Roman Zippel wrote:
> Hi,
>
> On Wed, 20 Jun 2007, Kenneth Zadeck wrote:
>
>
>> If we add the dead note there we are asserting that the value is
>> modified by the caller. however it might not be and someone could write
>> a piece of asm right after the call to use that reg if the person knew
>>
[EMAIL PROTECTED] wrote on 21/06/2007 15:44:27:
> Hello. i am Alberto
>
> I work with Gcc trees to modify c++ original code and dont find and i
> need documentation about trees because the web isnt enought information.
>
> Where are docs about gcc trees and macros to access it?
>
In GCC wiki you
Kenneth Zadeck <[EMAIL PROTECTED]> writes:
> @@ -3985,6 +3988,11 @@ df_note_bb_compute (unsigned int bb_inde
> = df_create_unused_note (insn, old_unused_notes,
> def, live, do_not_gen,
> artificial_
On Thu, Jun 21, 2007 at 10:14:55AM +0200, Uros Bizjak wrote:
> Hello H.J.!
>
> The testscase gcc.target/i386/sse2-vec-5.c you ported from mainline
> fails on gcc-4.2 branch because __builtin_ia32_vec_ext_v16qi builtin
> does not exist in gcc-4.2. This builtin corresponds to pextrb insn
> that was
On 6/21/07, H. J. Lu <[EMAIL PROTECTED]> wrote:
> Also, the definition of __builtin_ia32_vec_ext_v16qi in the mainline
> should be enabled only for OPTION_MASK_ISA_SSE4_1, as current
> definition is also enabled for SSE2:
>
> def_builtin (OPTION_MASK_ISA_SSE2, "__builtin_ia32_vec_ext_v16qi",
>
Hello,
I get the following bootstrap comparison failure on powerpc64
for Ada (--enable-languages=ada) with BOOT_CFLAGS='-O2'.
Revital
make[2]: Entering directory `/home/revital/mainline_ccp/build'
make[3]: Entering directory `/home/revital/mainline_ccp/build'
rm -f stage_current
make[3]: Leavi
+
+ /* However a may or must clobber still still needs to
+kill the reg. */
Add here "so that REG_DEAD notes are later placed appropriately". Ok,
thanks!
Paolo
On Mon, Jun 18, 2007 at 04:46:10PM +1000, Ben Elliston wrote:
> On Sat, 2007-06-16 at 06:17 -0700, H. J. Lu wrote:
>
> > BTW, an x86 DFP configure bug was reported 3 months ago. But it still
> > hasn't benen fixed. I opened a DFP bug report:
> >
> > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32
Hello!
Is there a way to add automatically updated SVN revision number to gcc
version string? Something similar to $Revision$ in RCS?
I think it would be quite informative if during development phase "gcc
--version" would report it like:
gcc --version
gcc (GCC) 4.3.0 20070621 (ex
;gcc
> --version" would report it like:
>
> gcc --version
> gcc (GCC) 4.3.0 20070621 (experimental) Revision X
>
> Perhaps it can also include branch name.
>
See
http://gcc.gnu.org/ml/gcc-testresults/2007-06/msg00966.html
I got
[EMAIL PROTECTED] applied]$ /usr/g
if during development phase[...]
> gcc --version
> gcc (GCC) 4.3.0 20070621 (experimental) Revision X
I would like this as well. Maybe something along the following would work:
STRING=""
if [ -d "$CONFIGURE/.svn" -a -n "`svn 2>&1`" ]; then
> I get the following bootstrap comparison failure on powerpc64
> for Ada (--enable-languages=ada) with BOOT_CFLAGS='-O2'.
>
> Revital
>
> make[2]: Entering directory `/home/revital/mainline_ccp/build'
> make[3]: Entering directory `/home/revital/mainline_ccp/build'
> rm -f stage_current
> make[3]
Paolo Bonzini wrote:
> +
> + /* However a may or must clobber still still needs to
> + kill the reg. */
>
> Add here "so that REG_DEAD notes are later placed appropriately". Ok,
> thanks!
>
> Paolo
so is this an ok to commit with this change?
> > make[2]: Entering directory `/home/revital/mainline_ccp/build'
> > make[3]: Entering directory `/home/revital/mainline_ccp/build'
> > rm -f stage_current
> > make[3]: Leaving directory `/home/revital/mainline_ccp/build'
> > Comparing stages 2 and 3
> > warning: ./cc1-checksum.o differs
> > Boot
> Which revision? The Ada compiler bootstraps fine on i586 and x86-64 at
> revision 125912:125915M (i.e with structural alias analysis enabled).
>
revision 125915.
Thanks,
Revital
> >
> > Which revision? The Ada compiler bootstraps fine on i586 and x86-64 at
> > revision 125912:125915M (i.e with structural alias analysis enabled).
>
> Note that if cc1-checksum.o differs, it likely means the issue is
unrelated to
> Ada.
I am now bootstrapping only c. If that will pass OK
> Note that if cc1-checksum.o differs, it likely means the issue is unrelated
> to Ada.
cc1-checksum.o very offen differs on my machine, it doesn't stop the build.
--
Eric Botcazou
GCC) 4.3.0 20070621 (experimental) Revision X
Perhaps it can also include branch name.
I have the following in my build script:
echo $VERSION > $BLDDIR/gcc/gcc/DEV-PHASE
$VERSION shows up in place of "experimental".
--
Michael Eager[EMAIL PROTECTED]
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
> I am now bootstrapping only c. If that will pass OK I can check Ada on
> an older revision if you wish.
I'm not sure that would really help in this case. The fact that x86 and
x86-64 are both clean with structural alias analysis would seem to show
that there is no fundamental bad interaction
Eric Botcazou <[EMAIL PROTECTED]> wrote on 21/06/2007 21:10:15:
> > I am now bootstrapping only c. If that will pass OK I can check Ada on
> > an older revision if you wish.
>
> I'm not sure that would really help in this case. The fact that x86 and
> x86-64 are both clean with structural alia
I submitted the first patch for the function argument infrastructure change
over at gcc-patches: http://gcc.gnu.org/ml/gcc-patches/2007-06/msg01569.html
--
Michael Meissner, AMD
90 Central Street, MS 83-29, Boxborough, MA, 01719, USA
[EMAIL PROTECTED]
michael.a wrote:
>
> Will likely be a good while before I can report whether simply knocking
> out the errors cause any run-time issues.
Is there some reason why stdarg.h would not be on my system (amd64 ubuntu)
I can find it in the various gcc source trees (apparently gcc brings its
own) ...
On Thu, Jun 21, 2007 at 03:08:00PM -0700, michael.a wrote:
>
>
>
> michael.a wrote:
> >
> > Will likely be a good while before I can report whether simply knocking
> > out the errors cause any run-time issues.
>
> Is there some reason why stdarg.h would not be on my system (amd64 ubuntu)
>
>
Meissner, Michael wrote:
>
>
> You probably should root around to find out why it isn't installed. I
> would
> suspect you did not install the appropriate development packages or
> somehow
> your compilation system is messed up.
>
I rooted thoroughly, not wanting to make this post for fear
michael.a wrote:
>
>
> I guess I will have to sort out why the compiler isn't finding it (any
> advice is welcome -- just for the record, I did a straight install from
> packaged sources with previous gcc installs removed before hand)
>
>
Actually, funny story... I was actually looking for
Herman Geza wrote:
struct A {
float x, y;
};
struct B {
float x, y;
};
int main() {
A a;
B &b = reinterpret_cast(a);
}
I get a type-punned warning for this code. However, A & B is exactly the
same type. Is the warning appropriate here?
Unfortunately gcc 4.3
Hi DJ,
By default all the constant variables will be stored in the far memory
('.frodata' section) and will be accessed using "LDE" instruction. The
non-initialized non-constant variables will be stored in near memory
('.nbss' section) and will be accessed using "MOV" instructions. The
initialize
32 matches
Mail list logo
