Snapshot gcc-4.7-20110820 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.7-20110820/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.7 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk
On Saturday 20 of August 2011 14:51:44 sudhakar govindavajhala wrote:
> Hi there,
>
> I am writing C++ code in Linux (2.6.18) using pthreads. glibc 2.5. gcc 4.1.2
>
> 2) I would like to translate SIGSEGV or SIGFPE to an exception in the
> program so that it can be caught at higher levels. Is th
sudhakar govindavajhala writes:
> I am writing C++ code in Linux (2.6.18) using pthreads. glibc 2.5. gcc 4.1.2
>
> 1) I understand that signals SIGFPE and SIGSEGV are sent to individual
> threads while SIGINT is sent to the whole process. How do I find out
> what signal is thread specific and wh
Gabriel Dos Reis writes:
> On Fri, Aug 19, 2011 at 11:17 PM, Ian Lance Taylor wrote:
>> Gabriel Dos Reis writes:
>>
>>> what would it do? There is no notion of `prototype' in C++ (as C
>>> programmers understand it).
>>> So, what would it mean to warn about something we can't take the
>>> nega
Hi there,
I am writing C++ code in Linux (2.6.18) using pthreads. glibc 2.5. gcc 4.1.2
1) I understand that signals SIGFPE and SIGSEGV are sent to individual
threads while SIGINT is sent to the whole process. How do I find out
what signal is thread specific and what signal is process wide. How
Adding this code:
C:\devel\gcc\gcc\config\i370>cvs diff i370.md
Index: i370.md
===
RCS file: c:\cvsroot/gcc/gcc/config/i370/i370.md,v
retrieving revision 1.21
diff -r1.21 i370.md
845a846,851
if (operands[1] == const0_rtx)
{
And here is the same debug info as last time ...
#include "config.h"
#include "system.h"
#include "coretypes.h"
#include "tm.h"
#include "rtl.h"
rtx
foo (rtx addr, int size, int n_refs)
{
int offset = 0;
switch (GET_CODE (addr))
{
case PRE_INC:
offset = (n_refs + 1) * size;
br
(like the 8 byte move from F'0'). I'll do my own investigation
of that and report that later.
Ok, the bad MVC:
MVC 112(8,13),=F'0'
is being generated by the movdi instruction:
;
; movdi instruction pattern(s).
;
(define_insn ""
[(set (match_operand:DI 0 "nonimmediate_operand" "=d,m,S")
