Hello.
I prepared patch in order to make parsing of the file
easier for analyze_brprob.py.
Martin
>From a3f87f718ef82026af070df06ce83d72a2f6661d Mon Sep 17 00:00:00 2001
From: marxin <mli...@suse.cz>
Date: Mon, 29 May 2017 15:00:42 +0200
Subject: [PATCH 1/2] Fix coding style.
gcc/ChangeLog:
2017-05-30 Martin Liska <mli...@suse.cz>
* predict.def: Fix GNU coding style.
---
gcc/predict.def | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/gcc/predict.def b/gcc/predict.def
index e96be12be4a..fcda6c48f11 100644
--- a/gcc/predict.def
+++ b/gcc/predict.def
@@ -194,12 +194,13 @@ DEF_PREDICTOR (PRED_FORTRAN_OVERFLOW, "Fortran overflow", PROB_ALWAYS,
of memory. This predictor only occurs when the user explicitly asked
for a return status. By default, the code aborts,
which is handled via PRED_NORETURN. */
-DEF_PREDICTOR (PRED_FORTRAN_FAIL_ALLOC, "Fortran fail alloc", PROB_VERY_LIKELY, 0)
+DEF_PREDICTOR (PRED_FORTRAN_FAIL_ALLOC, "Fortran fail alloc",
+ PROB_VERY_LIKELY, 0)
/* Predictor is used for an allocation of an already allocated memory or
deallocating an already deallocated allocatable. */
-DEF_PREDICTOR (PRED_FORTRAN_REALLOC, \
- "Fortran repeated allocation/deallocation", PROB_LIKELY, 0)
+DEF_PREDICTOR (PRED_FORTRAN_REALLOC, "Fortran repeated allocation/deallocation",
+ PROB_LIKELY, 0)
/* Branch leading to an I/O failure status are unlikely. This predictor is
used for I/O failures such as for invalid unit numbers. This predictor
--
2.12.2
