setting a breakpoint on a break statement

2007-03-14 Thread Tristan Gingold
Hi, in some cases, a breakpoint can't be set on a continue or break statement. Here is a simple example: void foc (void) { int a, i; for (i = 1; i <= 10; i++) { if (i < 3) a = 1; else break; // line 9 a = 5; } } int main(void) { foc (); } The reason is quie

Re: setting a breakpoint on a break statement

2007-03-15 Thread Tristan Gingold
On Mar 14, 2007, at 3:16 PM, Ian Lance Taylor wrote: Tristan Gingold <[EMAIL PROTECTED]> writes: in some cases, a breakpoint can't be set on a continue or break statement. Here is a simple example: The reason is quiet simple: even at -O0 -g, there is no insn (and no BB) corre

Re: Bug 29609

2007-04-26 Thread Tristan Gingold
On Apr 26, 2007, at 3:07 PM, Claus Fischer wrote: Dear GCC folks, may I humbly put in a word for my dear bug 29609, which is very close to my heart? I write most of my C code in the style if (!do_something(...)) goto failure_handler; and letting the debugger stop at the 'goto'

Re: obsolete targets

2014-07-10 Thread Tristan Gingold
On 10 Jul 2014, at 04:23, Trevor Saunders wrote: > Hi, > > I've noticed that the following targets are built in config-list.mk with > --enable-obsolete > i686-interix3 - doesn't appear to actually require --enable-obsolete > though, should it be marked as obsolete in config.gcc? > score-* and p

Re: Trouble trying to test GCC on a simulator

2014-09-08 Thread Tristan Gingold
On 08 Sep 2014, at 12:01, Pierre-Marie de Rodat wrote: > Hello, > > I would like to test a GCC patch on the platform it is supposed to affect > (PowerPC). In order to to this, I'm using the following documentation: > >https://gcc.gnu.org/simtest-howto.html > > However, after fresh CVS ch

Re: Trouble trying to test GCC on a simulator

2014-09-08 Thread Tristan Gingold
On 08 Sep 2014, at 16:51, Pierre-Marie de Rodat wrote: > On 09/08/2014 12:26 PM, Tristan Gingold wrote: >> CVS ? Binutils (and gdb) are now using git: > > Huh! I knew this, but not being a daily CVS user, I though the commands in > the documentation would get a binutil

Changing base compiler requirement for bootstrapping GNAT

2017-01-19 Thread Tristan Gingold
Is it ok to require gcc 4.9 (3 years old) or later to build GNAT ? We plan to use gcc exceptions within the GNAT front-end (previously we were using a FE specific exception mechanism). This requires a matching implementation in the runtime, which was last changed for gcc 4.9 Our idea is to compl

Re: Changing base compiler requirement for bootstrapping GNAT

2017-01-19 Thread Tristan Gingold
> On 19 Jan 2017, at 11:46, Richard Biener wrote: > > On Thu, Jan 19, 2017 at 11:11 AM, Tristan Gingold wrote: >> Is it ok to require gcc 4.9 (3 years old) or later to build GNAT ? >> >> We plan to use gcc exceptions within the GNAT front-end (previously we w

Re: Changing base compiler requirement for bootstrapping GNAT

2017-01-19 Thread Tristan Gingold
> On 19 Jan 2017, at 13:33, Jakub Jelinek wrote: > > On Thu, Jan 19, 2017 at 01:26:32PM +0100, Andreas Schwab wrote: >> On Jan 19 2017, Tristan Gingold wrote: >> >>> Is it ok to require gcc 4.9 (3 years old) or later to build GNAT ? >> >> The newe

Re: Changing base compiler requirement for bootstrapping GNAT

2017-01-19 Thread Tristan Gingold
> On 19 Jan 2017, at 12:31, Richard Biener wrote: > > On Thu, Jan 19, 2017 at 12:04 PM, Tristan Gingold wrote: >> >>> On 19 Jan 2017, at 11:46, Richard Biener wrote: >>> >>> On Thu, Jan 19, 2017 at 11:11 AM, Tristan Gingold >>> wrote

Re: Changing base compiler requirement for bootstrapping GNAT

2017-01-23 Thread Tristan Gingold
> On 19 Jan 2017, at 13:33, Jakub Jelinek wrote: > > On Thu, Jan 19, 2017 at 01:26:32PM +0100, Andreas Schwab wrote: >> On Jan 19 2017, Tristan Gingold wrote: >> >>> Is it ok to require gcc 4.9 (3 years old) or later to build GNAT ? >> >> The newe

Re: Revision 180821 breaks bootstrap

2011-11-03 Thread Tristan Gingold
On Nov 3, 2011, at 3:23 PM, Richard Guenther wrote: > On Thu, Nov 3, 2011 at 3:22 PM, Richard Guenther > wrote: >> On Thu, Nov 3, 2011 at 3:20 PM, Dominique Dhumieres >> wrote: >>> Revision 180821 breaks bootstrap on x86_64-apple-darwin10: >>> >>> ../../work/gcc/collect2.c: In function 'int m

Re: CVS/SVN binutils and gcc on MacOS X?

2009-09-07 Thread Tristan Gingold
On Sep 4, 2009, at 11:06 PM, Stefan Dösinger wrote: Hi, I tried to install binutils from CVS and the gcc SVN code on my mac to test my msvc_prologue work there, but I ran into an interesting problem: When using the SVN gcc with my own as, I cannot compile any files: Assembler messages: Fata

Re: apple blocks extension

2009-09-15 Thread Tristan Gingold
On Sep 15, 2009, at 3:46 PM, Steven Bosscher wrote: Hi, The status is that there is no status, unfortunately (it's an interesting extension...). This extension is not presently implemented in the FSF GCC. AFAIU there is no reason to believe Apple will contribute patches to implement it. I t

Re: Idea for Google Summer Code : C Compiler for EFI Byte Code implement in gcc

2010-03-03 Thread Tristan Gingold
On Mar 3, 2010, at 11:36 AM, Andrew Haley wrote: > On 03/03/2010 04:52 AM, b95705...@ntu.edu.tw wrote: > >> I am highly interestd in implementing C compiler for EFI Byte Code in >> gcc and participate in Google Summer Code. >> >> EFI is a much larger, more complex,OS-like replacement for the ol

Re: (un)aligned accesses on x86 platform.

2010-03-16 Thread Tristan Gingold
On Mar 16, 2010, at 3:50 PM, H.J. Lu wrote: > 2010/3/8 Paweł Sikora : >> hi, >> >> during development a cross platform appliacation on x86 workstation >> i've enabled an alignemnt checking [1] to catch possible erroneous >> code before it appears on client's sparc/arm cpu with sigbus ;) >> >> i

Re: (un)aligned accesses on x86 platform.

2010-03-16 Thread Tristan Gingold
On Mar 16, 2010, at 4:37 PM, Alexey Salmin wrote: >>> I am interested in an -mstrict-alignment option for x86. >> >> Not sure it will be useful. The libc still does unaligned accesses IIRC. >> > > Wow. What for? Well, simply because it is not compiled with strict alignment. There might also

Re: Idea for Google Summer Code : C Compiler for EFI Byte Code implement in gcc

2010-03-19 Thread Tristan Gingold
On Mar 19, 2010, at 1:33 PM, b95705...@ntu.edu.tw wrote: > Hello Tristan, > >> I think the main issue is that EFI C dialect is not ANSI-C compliant: the >> size of pointer is determined >> at the run-time and therefore the layout of the structure is not static. >> Gcc doesn't support this mod

Re: Idea for Google Summer Code : C Compiler for EFI Byte Code implement in gcc

2010-03-19 Thread Tristan Gingold
On Mar 19, 2010, at 12:48 PM, b95705...@ntu.edu.tw wrote: > I use Macbook with refit ,and its EFI shell version is 1.10.I have read > some related information but I don't find how to launch EBC virture machine. > I am truely want to know how could I launch it with fully appreciation. > And I am wo

Re: gcc 4.5.0 vms-gcc_shell_handler.c needs #define __NEW_STARLET

2010-05-03 Thread Tristan Gingold
On May 3, 2010, at 12:02 PM, Jay K wrote: > > /src/gcc-4.5.0/libgcc/../gcc/config/alpha/vms-gcc_shell_handler.c: In > function 'get_dyn_handler_pointer': > /src/gcc-4.5.0/libgcc/../gcc/config/alpha/vms-gcc_shell_handler.c:73:3: > error: 'PDSCDEF' undeclared (first use in this function) > /src/

Re: gcc 4.5.0 stddef.h clobbers __size_t with #define, breaks VMS (code already avoids similar on FreeBSD)

2010-05-03 Thread Tristan Gingold
On May 3, 2010, at 12:33 PM, Jay K wrote: > > VMS decc$types.h: > > typedef unsigned int __size_t; > > but with GCC 4.5.0 this preprocesses as: > > typedef unsigned int ; > > and there are ensuing errors e.g. when compiling gcc/libiberty/regex.c > > probably because of: > > /us

Re: PATCH: 2 stage BFD linker for LTO plugin

2010-12-07 Thread Tristan Gingold
On Dec 6, 2010, at 6:23 PM, Dave Korn wrote: > Tristan, sorry, you must be sick of hearing from me by now, No, not really :-) > but I notice the > branch was still labile a couple of hours ago... it would be really good if we > could get HJ's patch approved and backported before you spin the re

Re: [RFC / musing] Scoped exception handling in Linux userspace?

2013-07-18 Thread Tristan Gingold
On Jul 19, 2013, at 2:26 AM, Andy Lutomirski wrote: > Windows has a feature that I've wanted on Linux forever: stack-based > (i.e. scoped) exception handling. The upshot is that you can do, > roughly, this (pseudocode): [...] Indeed Windows and OpenVMS have such a mechanism. That's clean and l

Re: [buildrobot] alpha64-dec-vms / alpha-dec-vms

2013-11-26 Thread Tristan Gingold
On 26 Nov 2013, at 04:23, Jan-Benedict Glaw wrote: > Hi! > > Build log is available at > http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=36942 > http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=40027 Yes, we are aware of that. Basically, the openvms configuration

arm ttype encoding

2013-12-13 Thread Tristan Gingold
Hi, we are currently working on the use of the arm ehabi for Ada exceptions, and we aren't sure about which encoding has to be used for ttype. The patch http://gcc.gnu.org/ml/gcc-patches/2011-09/msg00765.html explains that on `Older ARM EABI toolchains set this value [ttype_encoding] incorrectly`

Re: Switching to C++ by default in 4.8

2012-04-04 Thread Tristan Gingold
On Apr 3, 2012, at 7:37 PM, Diego Novillo wrote: > > We would like to start the process to make GCC 4.8 build in C++ mode by > default. > > The mechanics of the change are simple enough. I volunteer to test changing > the default on all primary targets (assuming I can get them from the GCC

Re: Switching to C++ by default in 4.8

2012-04-04 Thread Tristan Gingold
On Apr 4, 2012, at 3:12 PM, Ian Lance Taylor wrote: > Tristan Gingold writes: > >> On Apr 3, 2012, at 7:37 PM, Diego Novillo wrote: >> >>> >>> We would like to start the process to make GCC 4.8 build in C++ mode by >>> default. >>>

Re: Switching to C++ by default in 4.8

2012-04-04 Thread Tristan Gingold
On Apr 4, 2012, at 4:37 PM, Gabriel Dos Reis wrote: > On Wed, Apr 4, 2012 at 8:32 AM, Tristan Gingold wrote: > >> For Alpha, gas crashes during libstdc++ build. From initial investigation, >> this looks manageable. But Alpha object format is quite old, and has no >>

[Wiki] Building GCC in C++

2012-04-10 Thread Tristan Gingold
Hi, I have added two entries: alpha64-dec-openvms - currently as failed. I still have to investigate the support of weak symbols by the assembler ia64-hp-openvms - pass. But it requires some patches for Ada. Tristan.

Re: [Wiki] Building GCC in C++

2012-04-10 Thread Tristan Gingold
On Apr 10, 2012, at 3:07 PM, Diego Novillo wrote: > On 4/10/12 8:41 AM, Tristan Gingold wrote: >> Hi, >> >> I have added two entries: >> alpha64-dec-openvms - currently as failed. I still have to investigate the >> support of weak symbols by the assembler &

Re: regression due to r187199 explow.c? in target ia64-hp-hpux11.23.

2012-05-30 Thread Tristan Gingold
Hi, did you try with this patch: http://gcc.gnu.org/ml/gcc-patches/2012-05/msg00970.html Tristan. On May 29, 2012, at 12:23 PM, Mailaripillai, Kannan Jeganathan wrote: > Hi, > > This modification (assertion) is causing failure in ia64-hp-hpux11.23: > > r187199 | rsandifo | 2012-05-05 10:41:4

Re: regression due to r187199 explow.c? in target ia64-hp-hpux11.23.

2012-06-06 Thread Tristan Gingold
the original post: > http://gcc.gnu.org/ml/gcc/2012-05/msg00371.html > > Regards, > Kannan > > -Original Message- > From: Mailaripillai, Kannan Jeganathan > Sent: Wednesday, May 30, 2012 2:44 PM > To: 'Tristan Gingold' > Cc: gcc@gcc.gnu.org > Subj

Re: regression due to r187199 explow.c? in target ia64-hp-hpux11.23.

2012-06-06 Thread Tristan Gingold
o! Tristan. > > Regards, > Kannan > > -Original Message- > From: Tristan Gingold [mailto:ging...@adacore.com] > Sent: Wednesday, June 06, 2012 1:17 PM > To: Mailaripillai, Kannan Jeganathan > Cc: gcc@gcc.gnu.org > Subject: Re: regression due to r187199 explow.

Re: regression due to r187199 explow.c? in target ia64-hp-hpux11.23.

2012-06-06 Thread Tristan Gingold
is failing due to this. I haven't tried to build for ia64-hpux, only for ia64-openvms (which doesn't support omp). What is the backtrace ? Tristan. > > Regards, > Kannan > > -Original Message- > From: Mailaripillai, Kannan Jeganathan > Sent: Wednesday, J

Re: regression due to r187199 explow.c? in target ia64-hp-hpux11.23.

2012-06-07 Thread Tristan Gingold
:0 in compile () > #30 0x6571940:0 in finalize_compilation_unit () > #31 0x51bc8e0:0 in c_write_global_declarations () > #32 0x9c63b30:0 in compile_file () > #33 0x9c6b470:0 in do_compile () > #34 0x9c6b9c0:0 in toplev_main (argc=49, argv=0x7fffeee8) > #35 0xf564740:0 in main (argc

Re: libbacktrace and darwin

2012-10-05 Thread Tristan Gingold
On Oct 4, 2012, at 11:23 PM, Ian Lance Taylor wrote: > On Thu, Oct 4, 2012 at 1:32 PM, Jack Howarth wrote: >> Is libbacktrace currently functional in gcc trunk and is it expected >> to function on darwin? While I could understand it not working on installed >> binaries of FSF gcc that were str

Re: libbacktrace and darwin

2012-10-05 Thread Tristan Gingold
On Oct 5, 2012, at 11:37 AM, Richard Guenther wrote: > On Fri, Oct 5, 2012 at 9:15 AM, Tristan Gingold wrote: >> >> On Oct 4, 2012, at 11:23 PM, Ian Lance Taylor wrote: >> >>> On Thu, Oct 4, 2012 at 1:32 PM, Jack Howarth >>> wrote: >>>> Is

Re: Implementing VMX128 AltiVec Variant

2007-08-21 Thread Tristan Gingold
On Aug 21, 2007, at 11:49 PM, Gordan Bobic wrote: These are the only place I found references to them, apart from the files in the gcc/ada directory: gcc/ada/g-alveop.adb gcc/ada/g-alveop.ads gcc/ada/g-alleve.adb gcc/ada/g-alleve.ads I ignored these - I am making a rash assumption here tha