The patch does not cause failures on AIX. Is it removing explicit
references to /lib and /usr/lib?
It seems more appropriate for GCC 15.
Thanks for alerting me to the patch to test on AIX. AIX is in CFarm.
Thanks David
On Tue, Apr 16, 2024 at 7:49 PM Andrew Pinski (QUIC) <
If the fixes remove the failures on AIX, then the patch to disable the
tests also can be reverted.
Thanks, David
On Wed, Jan 17, 2024 at 8:06 PM Alexandre Oliva wrote:
> David,
>
> On Jan 7, 2024, "Kewen.Lin" wrote:
>
> > As PR113100 shows, the unbiasing introduced by r14-6737 can
> > cause
On Sat, Dec 16, 2023 at 7:04 PM Jonathan Wakely wrote:
> On Sun, 17 Dec 2023 at 00:02, Jonathan Wakely wrote:
> >
> > On Sat, 16 Dec 2023 at 23:06, David Edelsohn wrote:
> > >
> > > On Sat, Dec 16, 2023 at 4:44 PM Jakub Jelinek
> wrote:
> > >>
On Sat, Dec 16, 2023 at 4:44 PM Jakub Jelinek wrote:
> On Sat, Dec 16, 2023 at 04:24:13PM -0500, David Edelsohn wrote:
> > AIX stdio.h defines fileno as a macro although there is a symbol in libc.
> >
> > I think that print.cc at least needs to
> >
> >
>
Hi, Jonathan
Unfortunately this patch broke bootstrap on AIX.
In file included from /tmp/GCC/gcc/include-fixed/wchar.h:64,
from
/tmp/GCC/powerpc-ibm-aix7.2.5.0/libstdc++-v3/include/cwchar:44,
from
, 2023 at 11:10 AM David Edelsohn wrote:
> Alex,
>
> This patch broke bootstrap on AIX. The stage1 compiler is not able to
> build a program and stage2 configure fails.
>
> Thanks, David
>
>
Alex,
This patch broke bootstrap on AIX. The stage1 compiler is not able to
build a program and stage2 configure fails.
Thanks, David
On Tue, Nov 21, 2023 at 8:51 AM Arsen Arsenović wrote:
>
> Arsen Arsenović writes:
>
> > Bruno Haible writes:
> >
> >> Arsen Arsenović wrote:
> >>> Comparing stages 2 and 3
> >>> Bootstrap comparison failure!
> >>> gettext/libasprintf/autosprintf.o differs
> >>> make[2]: ***
itself with the different stages of the
compiler, so the appended random number changes.
Thanks, David
On Mon, Nov 20, 2023 at 4:23 PM Arsen Arsenović wrote:
>
> David Edelsohn writes:
>
> > On Sun, Nov 19, 2023 at 5:15 PM Bruno Haible wrote:
> >
> >> David Ed
On Sun, Nov 19, 2023 at 5:15 PM Bruno Haible wrote:
> David Edelsohn wrote:
> > --disable-threads currently does not completely disable threads. Bruno
> is
> > suggesting --enable-threads=isoc that relies on mtx mutex functions in
> libc.
>
> Unfortunately, as s
On Fri, Nov 17, 2023 at 10:17 AM Arsen Arsenović wrote:
>
> David Edelsohn writes:
>
> > On Fri, Nov 17, 2023 at 3:46 AM Arsen Arsenović wrote:
> >
> >>
> >> David Edelsohn writes:
> >>
> >> > On Thu, Nov 16, 2023 at 5:52 PM Arsen A
On Fri, Nov 17, 2023 at 3:46 AM Arsen Arsenović wrote:
>
> David Edelsohn writes:
>
> > On Thu, Nov 16, 2023 at 5:52 PM Arsen Arsenović wrote:
> >
> > [snip]
> >> Sure, but my patch does insert --disable-shared:
> >>
> >> --8<-
On Thu, Nov 16, 2023 at 7:07 PM Bruno Haible wrote:
> David Edelsohn wrote:
> > > ibm-clang links against libpthread.a as well:
> > > $ ldd /opt/IBM/openxlC/17.1.1/bin/.ibm-clang.orig
> > > /opt/IBM/openxlC/17.1.1/bin/.ibm-clang.orig needs:
> &g
On Thu, Nov 16, 2023 at 5:52 PM Arsen Arsenović wrote:
>
> David Edelsohn writes:
>
> > On Thu, Nov 16, 2023 at 5:22 PM Arsen Arsenović wrote:
> >
> >>
> >> David Edelsohn writes:
> >>
> >> > Don't build with the dependent li
On Thu, Nov 16, 2023 at 5:47 PM Bruno Haible wrote:
> Hi David,
>
> > the default, distributed libintl library will not allow GCC to be built
> > with NLS enabled.
>
> The problem is this configure test from gettext.m4
>
> checking for GNU gettext in libintl... no
>
> It should say
>
>
On Thu, Nov 16, 2023 at 5:22 PM Arsen Arsenović wrote:
>
> David Edelsohn writes:
>
> > Don't build with the dependent libraries in tree. Don't build the
> > dependent libraries as shared libraries. The libraries are already built
> > and in /opt/cfarm, as mention
On Thu, Nov 16, 2023 at 1:52 PM Bruno Haible wrote:
> David Edelsohn wrote:
> > I manually commented out HAVE_PTHREAD_API from config.h and produced a
> > libintl.a without references to pthreads.
>
> Good finding!
>
> Commenting out HAVE_PTHREAD_API from config.h is a
ntoo Developer UID) (trust ultimate) created at
> 2023-11-16T19:47:16+0100 using EDDSA]]
> >
> > David Edelsohn writes:
> >
> >> On Wed, Nov 15, 2023 at 9:22 AM Arsen Arsenović
> wrote:
> >>
> >>>
> >>> David Edelsohn writes:
distributed.
Thanks, David
On Thu, Nov 16, 2023 at 1:01 PM David Edelsohn wrote:
> Bruno,
>
> The issue appears to be that intl/gnulib-lib/{mbrtowc.c,setlocale_null.c}
> include pthread.h based on HAVE_PTHREAD_API, which is defined as 1 in
> intl/config.h build directory des
Bruno,
The issue appears to be that intl/gnulib-lib/{mbrtowc.c,setlocale_null.c}
include pthread.h based on HAVE_PTHREAD_API, which is defined as 1 in
intl/config.h build directory despite requesting --disable-pthreads.
Thanks, David
On Thu, Nov 16, 2023 at 11:35 AM David Edelsohn wrote:
>
On Thu, Nov 16, 2023 at 11:58 AM Richard Biener
wrote:
>
>
> Am 16.11.2023 um 17:00 schrieb David Edelsohn :
>
>
> Bruno,
>
> I have been able to tweak the environment and build gettext and libintl.
> With the updated libintl and environment, GCC reliably does
812 D _libintl_setlocale_null_r
824 D _libintl_setlocale_null
On Thu, Nov 16, 2023 at 11:00 AM David Edelsohn wrote:
> Bruno,
>
> I have been able to tweak the environment and build gettext and libintl.
> With the updated libintl and environment, GCC reliably does
.
This is a regression in NLS support in GCC.
Thanks, David
On Wed, Nov 15, 2023 at 5:39 PM Bruno Haible wrote:
> David Edelsohn wrote:
> > I am using my own install of GCC for a reason.
>
> I have built GNU gettext 0.22.3 in various configurations on the AIX 7.1
> and 7.3 machines in the compil
On Wed, Nov 15, 2023 at 4:22 PM Bruno Haible wrote:
> David Edelsohn wrote:
> > When I try to configure gettext-0.22.3, I receive the following error:
> >
> > checking for socklen_t equivalent... configure: error: Cannot find a type
> > to use in place of socklen
On Wed, Nov 15, 2023 at 9:22 AM Arsen Arsenović wrote:
>
> David Edelsohn writes:
>
> > GCC had been working on AIX with NLS, using "--with-included-gettext".
> > --disable-nls gets past the breakage, but GCC does not build for me on
> AIX
> > with
wrote:
> [CCing bug-gettext]
>
> David Edelsohn wrote in
> <https://gcc.gnu.org/pipermail/gcc-patches/2023-November/636558.html>:
> > The current gettext-0.22.3 fails to build for me on AIX.
>
> Here are some hints to get a successful build of GNU gettext on AIX:
&
On Wed, Nov 15, 2023 at 9:22 AM Arsen Arsenović wrote:
>
> David Edelsohn writes:
>
> > GCC had been working on AIX with NLS, using "--with-included-gettext".
> > --disable-nls gets past the breakage, but GCC does not build for me on
> AIX
> > with
On Tue, Nov 14, 2023 at 6:09 PM Arsen Arsenović wrote:
> Hi David,
>
> David Edelsohn writes:
>
> > Arsen,
> >
> > Unfortunately this broke bootstrap on AIX.
> >
> > I had not seen this series of patches.
>
> I've added Bruno to CC as the libin
Arsen,
Unfortunately this broke bootstrap on AIX.
I had not seen this series of patches.
David
/gimple-harden-control-flow.cc*
@@ -23,6 +23,7 @@ along with GCC; see the file COPYING3. If not see
#include "system.h"
#include "coretypes.h"
#include "backend.h"
+#include "memmodel.h"
#include "tm_p.h"
#include "tree.h"
#i
This patch broke bootstrap on AIX because ASM_GENERATE_INTERNAL_LABEL can
embed target-specific functions. Fixed by including tm_p.h.
Thanks, David
* gimple-harden-control-flow.cc: Include tm_p.h.
*diff --git a/gcc/gimple-harden-control-flow.cc
b/gcc/gimple-harden-control-flow.cc*
[Resending from correct email.]
Hi, Surya
Thanks for working on this issue and creating a patch.
It helps if you explicitly send patches to Segher and me, and copy
gcc-patches.
+/* Return true if insn is a non-permuting load/store. */
+static bool
+non_permuting_mem_insn (swap_web_entry
Hi, Surya
Thanks for working on this issue and creating a patch.
It helps if you explicitly send patches to Segher and me, and copy gcc-patches.
+/* Return true if insn is a non-permuting load/store. */
+static bool
+non_permuting_mem_insn (swap_web_entry *insn_entry, unsigned int i)
+{
+
On Thu, Oct 12, 2023 at 4:24 AM Michael Meissner
wrote:
> I was building a cross compiler to PowerPC on my x86_86 workstation with
> the
> latest version of GCC on October 11th. I could not build the compiler on
> the
> x86_64 system as it died in building libgcc. I looked into it, and I
>
On Tue, Oct 10, 2023 at 9:29 PM Jiufu Guo wrote:
> Hi,
>
> There are some piece of code like below in rs6000.cc:
>
> ...
> if (xx)
>return x;
> else if (yy)
>return y;
> ... //else if chain
> else
>return d;
>
> Using early outs would be more preferable for this kind of code.
>
On Tue, Oct 10, 2023 at 4:23 AM HAO CHEN GUI wrote:
> Hi David,
>
> Thanks for your review comments.
>
> 在 2023/10/9 23:42, David Edelsohn 写道:
> > #define MOVE_MAX (! TARGET_POWERPC64 ? 4 : 8)
> > #define MAX_MOVE_MAX 8
> > +#define MOVE_MAX_P
On Sun, Oct 8, 2023 at 10:30 PM HAO CHEN GUI wrote:
> Hi,
> This patch enables vector mode for memory equality compare by adding
> a new expand cbranchv16qi4 and implementing it. Also the corresponding
> CC reg and compare code is set in rs6000_generate_compare. With the
> patch, 16-byte
On Thu, Oct 5, 2023 at 12:14 AM Jiufu Guo wrote:
> Hi,
>
> As mentioned in PR108338, on p9, we could use mtvsrws to implement
> the bitcast from SI to SF (or lowpart DI to SF).
>
> For example:
> *(long long*)buff = di;
> float f = *(float*)(buff);
>
> "sldi 9,3,32 ; mtvsrd 1,9 ; xscvspdpn
On Thu, Oct 5, 2023 at 12:50 AM Jiufu Guo wrote:
> Hi,
>
> Currently, we have the pattern "movsf_from_si2" which was trying
> to support moving high part DI to SF.
>
> But current pattern only accepts "ashiftrt":
> XX:SF=bitcast:SF(subreg(YY:DI>>32),0), but actually "lshiftrt" should
> also be
Hi, Siddhesh
Thanks for working on this and fine-tuning the original proposed text. It
looks good to me. Minor grammatical nit below.
Thanks, David
On Thu, Sep 28, 2023 at 7:59 AM Siddhesh Poyarekar
wrote:
> On 2023-09-28 12:55, Siddhesh Poyarekar wrote:
> > Define a security process and
le
> pointer ranges different.
>
> Andrew
>
> On 10/3/23 11:47, David Edelsohn wrote:
> > This patch caused a bootstrap failure on AIX.
> >
> > during GIMPLE pass: evrp
> >
> > /nasfarm/edelsohn/src/src/libgcc/libgcc2.c: In function '__gcc_bcmp':
> >
This patch caused a bootstrap failure on AIX.
during GIMPLE pass: evrp
/nasfarm/edelsohn/src/src/libgcc/libgcc2.c: In function '__gcc_bcmp':
/nasfarm/edelsohn/src/src/libgcc/libgcc2.c:2910:1: internal compiler error:
in get_irange, at value-range-storage.cc:343
2910 | }
| ^
On Wed, Sep 27, 2023 at 1:38 AM Kewen.Lin wrote:
> Hi,
>
> As PR111367 shows, with prefixed insn supported, some of
> checkings consider it's able to leverage prefixed insn
> for stack protect related load/store, but since we don't
> actually change the emitted assembly for 32 bit, it can
>
ode) on my linux also some other report it work on freebsd, just wait
> review :)
>
> https://gcc.gnu.org/pipermail/gcc-patches/2023-October/631785.html
>
> On Tue, Oct 3, 2023 at 2:07 AM Jeff Law wrote:
> >
> >
> >
> > On 10/2/23 12:03, Da
On Mon, Oct 2, 2023 at 1:59 PM Jeff Law wrote:
>
>
> On 10/2/23 11:20, David Edelsohn wrote:
> > Wang,
> >
> > The AWK portions of this patch broke bootstrap on AIX.
> >
> > Also, the AWK portions are common code, not RISC-V specific. I don't
&g
Wang,
The AWK portions of this patch broke bootstrap on AIX.
Also, the AWK portions are common code, not RISC-V specific. I don't see
anywhere that the common portions of the patch were reviewed or approved by
anyone with authority to approve the changes to the AWK files.
This patch should not
On Mon, Sep 25, 2023 at 10:52 PM Jiufu Guo wrote:
> Hi,
>
> Gentle ping...
>
> BR,
> Jeff (Jiufu Guo)
>
This is okay.
Thanks, David
>
> Jiufu Guo via Gcc-patches writes:
>
> > Hi,
> >
> > Gentle ping...
> >
> > BR,
> > Jeff (Jiufu Guo)
> >
> > Jiufu Guo writes:
> >
> >> Hi,
> >>
> >> If a
On Fri, Sep 29, 2023 at 2:09 PM Michael Meissner
wrote:
> When I first implemented COPYSIGN support in the power7 days, we did not
> have a
> copysign RTL insn, so I had to use UNSPEC to represent the copysign
> instruction. This patch removes those UNSPECs, and it uses the native RTL
>
g 2023 at 22:39, David Edelsohn wrote:
> > >
> > > Hi, Arsen
> > >
> > > This patch broke bootstrap because it has introduced a new GCC build
> requirement for autogen that is not a previous requirement to build GCC.
> Previously the repository has inc
Hi, Arsen
This patch broke bootstrap because it has introduced a new GCC build
requirement for autogen that is not a previous requirement to build GCC.
Previously the repository has included post-processed files.
+# AutoGen .
+.PHONY: update-version
+update-version:
+ cd ${bits_srcdir} &&
On Tue, Aug 15, 2023 at 7:07 PM Alexander Monakov
wrote:
>
> On Tue, 15 Aug 2023, Siddhesh Poyarekar wrote:
>
> > > Thanks, this is nicer (see notes below). My main concern is that we
> > > shouldn't pretend there's some method of verifying that arbitrary
> source
> > > code is "safe" to pass to
On Wed, Aug 9, 2023 at 1:33 PM Siddhesh Poyarekar
wrote:
> On 2023-08-08 10:30, Siddhesh Poyarekar wrote:
> >> Do you have a suggestion for the language to address libgcc,
> >> libstdc++, etc. and libiberty, libbacktrace, etc.?
> >
> > I'll work on this a bit and share a draft.
>
> Hi David,
>
>
On Wed, Aug 9, 2023 at 1:33 PM Siddhesh Poyarekar
wrote:
> On 2023-08-08 10:30, Siddhesh Poyarekar wrote:
> >> Do you have a suggestion for the language to address libgcc,
> >> libstdc++, etc. and libiberty, libbacktrace, etc.?
> >
> > I'll work on this a bit and share a draft.
>
> Hi David,
>
>
On Tue, Aug 8, 2023 at 1:36 PM Ian Lance Taylor wrote:
> On Tue, Aug 8, 2023 at 7:37 AM Jakub Jelinek wrote:
> >
> > BTW, I think we should perhaps differentiate between production ready
> > libraries (e.g. libgcc, libstdc++, libgomp, libatomic, libgfortran,
> libquadmath,
> > libssp) vs. e.g.
On Tue, Aug 8, 2023 at 10:07 AM Siddhesh Poyarekar
wrote:
> On 2023-08-08 10:04, Richard Biener wrote:
> > On Tue, Aug 8, 2023 at 3:35 PM Ian Lance Taylor wrote:
> >>
> >> On Tue, Aug 8, 2023 at 6:02 AM Jakub Jelinek via Gcc-patches
> >> wrote:
> >>>
> >>> On Tue, Aug 08, 2023 at 02:52:57PM
FOSS Best Practices recommends that projects have an official Security
policy stated in a SECURITY.md or SECURITY.txt file at the root of the
repository. GLIBC and Binutils have added such documents.
Appended is a prototype for a Security policy file for GCC based on the
Binutils document
Hi, Drew
Thanks for addressing this missed optimization.
The testcase includes an incorrect assumption: signed char, which
causes the testcase to fail on PowerPC.
Should the testcase be updated to specify signed char in the function
signatures or should -fsigned-char be added to the command
On Tue, Jun 13, 2023 at 2:16 PM Segher Boessenkool
wrote:
>
> Hi!
>
> On Tue, Jun 13, 2023 at 10:15:49AM +0800, Jiufu Guo wrote:
> > David Edelsohn writes:
> > >
> > > This definitely seems to be a better solution.
> > >
> > > The TARGE
On Mon, Jun 12, 2023 at 11:30 PM Jiufu Guo wrote:
>
>
> Hi David,
>
> David Edelsohn writes:
> > On Wed, Jun 7, 2023 at 9:55 PM Jiufu Guo wrote:
> >
> > Hi,
> >
> > This patch checks if a constant is possible to be rotated to/from a
> > p
Hi, Jiufu
This definitely seems to be a better solution.
The TARGET_CONST_ANCHOR change should not be part of this patch. Also
there is no ChangeLog for the patch.
This generally looks correct and consistent with other ports. I want
to give Segher a chance to double check it, if he wishes.
The rs6000 port has allocated a stack frame when debugging is enabled
on AIX since the earliest versions of the port. Apparently the
earliest versions of the debuggers for AIX had difficulty with
stackless frames.
Both AIX DBX and GDB support stackless frames on AIX, and IBM XLC,
OpenXL and LLVM
On Tue, Jun 6, 2023 at 5:19 AM Kewen.Lin wrote:
> Hi,
>
> As PR109932 shows, builtins __builtin_{un,}pack_vector_int128
> should be guarded under vsx rather than power7, as their
> corresponding bif patterns have the conditions TARGET_VSX
> and VECTOR_MEM_ALTIVEC_OR_VSX_P (V1TImode). This patch
On Tue, Jun 6, 2023 at 5:20 AM Kewen.Lin wrote:
> Hi,
>
> As PR110011 shows, when encoding 128 bits fp constant into
> toc, we adopts REAL_VALUE_TO_TARGET_LONG_DOUBLE which is
> to find the first float mode with LONG_DOUBLE_TYPE_SIZE
> bits of precision, it would be TFmode here. But the 128
>
On Wed, Jun 7, 2023 at 9:56 PM Jiufu Guo wrote:
> Hi,
>
> This patch checks if a constant is possible to be built by "li;rldic".
> We only need to take care of "negative li", other forms do not need to
> check.
> For example, "negative lis" is just a "negative li" with an additional
> shift.
>
>
On Wed, Jun 7, 2023 at 9:56 PM Jiufu Guo wrote:
> Hi,
>
> This patch checks if a constant is possible left/right cleaned on a rotated
> value from a negative value of "li/lis". If so, we can build the constant
> through "li/lis ; rldicl/rldicr".
>
> Bootstrap and regtest pass on ppc64{,le}.
>
On Wed, Jun 7, 2023 at 9:55 PM Jiufu Guo wrote:
> Hi,
>
> This patch checks if a constant is possible to be rotated to/from a
> negative
> value from "lis". If so, we could use "lis;rotldi" to build it.
> The positive value of "lis" does not need to be analyzed. Because if a
> constant can be
On Wed, Jun 7, 2023 at 9:55 PM Jiufu Guo wrote:
> Hi,
>
> This patch checks if a constant is possible to be rotated to/from a
> positive
> or negative value from "li". If so, we could use "li;rotldi" to build it.
>
> Bootstrap and regtest pass on ppc64{,le}.
> Is this ok for trunk?
>
> BR,
>
Hi, Jiufu
* config/rs6000/rs6000.cc (can_be_rotated_to_possitive_li): New
function.
(can_be_rotated_to_negative_li): New function.
(can_be_built_by_li_and_rotldi): New function.
(rs6000_emit_set_long_const): Call can_be_built_by_li_and_rotldi.
In English the word
On Tue, May 30, 2023 at 11:00 PM Jiufu Guo wrote:
>
> Gentle ping...
>
> Jiufu Guo via Gcc-patches writes:
>
> > Gentle ping...
> >
> > Jiufu Guo via Gcc-patches writes:
> >
> >> Hi,
> >>
> >> I'm thinking that we may enable this patch for stage1, so ping it.
> >>
On Sun, May 21, 2023 at 11:25 AM Andrew Pinski wrote:
> On Sun, May 21, 2023 at 11:17 AM David Edelsohn via Gcc-patches
> wrote:
> >
> > Hi, Andrew
> >
> > Thanks for this series of patches to improve do_store_flag.
> Unfortunately
> > this specific pat
Hi, Andrew
Thanks for this series of patches to improve do_store_flag. Unfortunately
this specific patch in the series has caused a bootstrap failure on
powerpc-aix. I bisected this failure to this specific patch. Note that I
am building as 32 bit, so this could be a specific issue about bit
On Fri, May 5, 2023 at 11:38 AM Tamar Christina
wrote:
> > -Original Message-
> > From: Jakub Jelinek
> > Sent: Friday, May 5, 2023 4:33 PM
> > To: Tamar Christina
> > Cc: Jeff Law ; David Edelsohn >;
> > GCC Patches
> > Subject: Re:
This patch has broken GCC bootstrap on AIX. It appears to rely upon, or
complain about, the command "seq":
/nasfarm/edelsohn/install/GCC12/bin/g++ -std=c++11 -g -DIN_GCC
-fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall
-Wno-narrowing -Wwrite-strings -Wcast-qual -Wno-format
On Mon, Jan 30, 2023 at 4:52 PM Gerald Pfeifer wrote:
> Hi David,
>
> the noticed the links to the AIX 4.3 and AIX 5L docs were broken and could
> not find a good replacement, though I did find one for AIX 7.2.
>
> How about the patch below?
>
Hi, Gerald
That change is fine with me.
Thanks,
This patch broke bootstrap on AIX due to its use of strchrnul(). It is an
extension available in Linux, but not all targets.
/src/src/gcc/cp/contracts.cc:213:21: error: 'strchrnul' was not declared in
this scope; did you mean 'strchr'?
213 | size_t role_len = strchrnul (role, ':') - role;
On Fri, Nov 18, 2022 at 7:20 AM Segher Boessenkool <
seg...@kernel.crashing.org> wrote:
> On Fri, Nov 18, 2022 at 02:35:30PM +0800, HAO CHEN GUI wrote:
> > 在 2022/11/17 21:24, David Edelsohn 写道:
> > > Why are you using zero_constant predicate instead of matching
>
On Thu, Nov 17, 2022 at 1:39 AM HAO CHEN GUI wrote:
> Hi,
> The patch enables have_cbrnachcc4 which is a flag in ifcvt.cc to
> indicate if branch by CC bits is invalid or not. The new expand pattern
> "cbranchcc4" is created which intend to match the pattern defined in
> "*cbranch",
perand 0 is a comparison operator. Operand 1 and operand 2 are the
> first and second operands of the comparison, respectively. Operand 3
> is the code_label to jump to.
>
> Gui Haochen
> Thanks
>
> 在 2022/11/16 11:04, David Edelsohn 写道:
> > It's great to a
On Tue, Nov 15, 2022 at 9:32 PM HAO CHEN GUI wrote:
> Hi,
> The patch enables have_cbrnachcc4 which is a flag in ifcvt.cc to
> indicate if branch by CC bits is invalid or not. As rs6000 already has
> "*cbranch" insn which does branching according to CC bits, the flag
> should be enabled and
> This patch does not change rs6000/s390 since I don't have machines to
> test them, but I suppose the default behavior is the same since they
> enable flag_unroll_loops at O2.
There are Power (rs6000) systems in the Compile Farm.
Trial Linux on Z (s390x) VMs are available through the Linux
This patch seems to have broken bootstrap on AIX. It seems to assume
methods that aren't guaranteed to be defined.
Thanks, David
libtool: compile: /tmp/GCC/./gcc/xgcc -B/tmp/GCC/./gcc/
-B/nasfarm/edelsohn/ins
tall/GCC/powerpc-ibm-aix7.2.5.0/bin/
-B/nasfarm/edelsohn/install/GCC/powerpc-ibm
This patch causes a bootstrap comparison failure on AIX. It apparently
does not cause a failure on PPC64BE Linux with the same ABI, so I suspect
that the failure may be related to the way that function aliases are
implemented on AIX, which doesn't have ELF symbol alias semantics.
"This change
On Fri, Sep 23, 2022 at 10:12 AM Thomas Neumann wrote:
> >
> > +static const bool in_shutdown = false;
> >
> > I'll let Jason or others decide if this is the right solution. It seems
> > that in_shutdown also could be declared outside the #ifdef and
> > initialized as "false".
>
> sure,
On Fri, Sep 23, 2022 at 9:38 AM Thomas Neumann wrote:
> > This patch broke bootstrap on AIX and probably other targets.
> >
> > #ifdef ATOMIC_FDE_FAST_PATH
> > #include "unwind-dw2-btree.h"
> >
> > static struct btree registered_frames;
> > static bool in_shutdown;
> > ...
> > #else
> >
> >
On Fri, Sep 23, 2022 at 9:38 AM Thomas Neumann wrote:
> > This patch broke bootstrap on AIX and probably other targets.
> >
> > #ifdef ATOMIC_FDE_FAST_PATH
> > #include "unwind-dw2-btree.h"
> >
> > static struct btree registered_frames;
> > static bool in_shutdown;
> > ...
> > #else
> >
> >
On Wed, Sep 7, 2022 at 7:45 AM Martin Liška wrote:
> Hi.
>
> The patch restores DWARF support for AIX target where XCOFF file container
> is used.
> Verified before and after the patch, gcc119 machine (AIX) could not build
> any run-time library,
> now it can.
>
> Ready to be installed?
>
at 12:31 PM David Edelsohn wrote:
> I fully support the plan to remove stabs support, but this patch broke
> bootstrap on AIX. It seems rather bad policy to remove support for a
> feature without ensuring that the removal does not negatively impact the
> targets touched by the patch. I
I fully support the plan to remove stabs support, but this patch broke
bootstrap on AIX. It seems rather bad policy to remove support for a
feature without ensuring that the removal does not negatively impact the
targets touched by the patch. I should have been explicitly copied on
these patches
On Thu, Aug 25, 2022 at 10:42 PM HAO CHEN GUI wrote:
>
> Hi David,
>
> On 25/8/2022 下午 10:01, David Edelsohn wrote:
> > On Thu, Aug 25, 2022 at 1:22 AM Kewen.Lin wrote:
> >>
> >> on 2022/8/25 11:37, HAO CHEN GUI wrote:
> >>> Hi,
> >>>
&
On Thu, Aug 25, 2022 at 1:22 AM Kewen.Lin wrote:
>
> on 2022/8/25 11:37, HAO CHEN GUI wrote:
> > Hi,
> >
> > On 24/8/2022 下午 1:24, Kewen.Lin wrote:
> >> Could you try to test with dg-options "-mdejagnu-cpu=power9 -mpowerpc64"
> >> all the time, but still
> >> having that has_arch_ppc64 effective
On Thu, May 26, 2022 at 1:52 AM Kewen.Lin wrote:
>
> Hi Haochen,
>
> on 2022/5/26 13:30, HAO CHEN GUI wrote:
> > Kewen,
> > Thanks so much for your advice. Just one question about effective-target.
> >
> > For the test cases, it needs both power10_ok and int128 support. I saw
> > some
> >
On Wed, Apr 27, 2022 at 8:22 AM Segher Boessenkool
wrote:
>
> Hi!
>
> Thank you for doing this testcase.
>
> On Wed, Apr 27, 2022 at 06:29:07PM +0800, Kewen.Lin wrote:
> > As discussed in PR105334, this patch is to add the test coverage for
> > the two recent fixes r12-8091 and r12-8226 from
On Mon, Apr 11, 2022 at 10:53 AM Alexandre Oliva wrote:
>
>
> The testcase was missing dg- before require-effective-target.
>
> While at that, I'm also pruning the excess-error warning I got when
> the test failed to be disabled because of the above. I suppose it
> might be useful for some
On Wed, Mar 23, 2022 at 5:33 AM Kewen.Lin wrote:
>
> Hi,
>
> As shown in PR104967, for some overload built-in function instance,
> if it requires a date type which isn't defined on the target, its
> fntype would be initialized as NULL. This patch is to consider
> this possibility in function
On Mon, Mar 21, 2022 at 5:13 AM Jiufu Guo wrote:
>
> Hi!
>
> There is a rare corner case: where __vector is followed only with ";"
> and near the end of the file.
>
> Like the case in PR101168:
> using vdbl = __vector double;
> #define BREAK 1
>
> For this case, "__vector double" is not followed
I don't have any objection, but the patch is FreeBSD-specific. You
are sending the patch from the FreeBSD organization, but I don't know
the authority structure within the organization. Andreas Tobler is
the FreeBSD maintainer for GCC, but I don't know his current status.
Thanks, David
On
On Tue, Mar 1, 2022 at 12:41 AM HAO CHEN GUI wrote:
>
> Hi,
>This patch enables absolute jump tables on PPC AIX and Linux. For AIX, the
> jump
> table is placed in data section. For Linux, it is placed in RELRO section when
> relocation is needed.
>
>Bootstrapped and tested on AIX,Linux
redundant target clause when modifying any testcase, please).
>
> Okay.
> >
> >> /* { dg-require-effective-target powerpc_p9vector_ok } */
> >> /* { dg-options "-mdejagnu-cpu=power9" } */
> >> +/* { dg-additional-options "-mbig" { target powe
On Tue, Feb 8, 2022 at 12:25 PM Jakub Jelinek wrote:
>
> Hi!
>
> The following testcase ICEs, because
> (const_vector:V4SI [
> (const_int 0 [0]) repeated x3
> (const_int -2147483648 [0x8000])
> ])
> is recognized as valid
On Mon, Feb 7, 2022 at 8:20 AM Jakub Jelinek wrote:
>
> On Fri, Feb 04, 2022 at 12:00:57PM -0500, David Edelsohn via Gcc-patches
> wrote:
> > > The following testcase FAILs when configured with
> > > --with-long-double-format=ieee . Only happens in the -std=c* mode
1 - 100 of 2062 matches
Mail list logo
