head	1.1;
access;
symbols;
locks; strict;
comment	@# @;


1.1
date	2026.07.06.13.49.07;	author adam;	state Exp;
branches;
next	;
commitid	l7vy4sE54XjO8BMG;


desc
@@


1.1
log
@librsvg: updated to 2.62.3

Version 2.62.3

librsvg crate version 2.62.3

librsvg-rebind crate version 0.3.0

- Remove loading limits from image-rs.  This means that raster
  images, when embedded in SVG documents, have no limits for their
  size or memory consumption.  The idea, for now, is that
  security-sensitive applications that use librsvg should do their own
  sandboxing if they want to impose memory limits.

- Fix the logic for whether gdk-pixbuf-query-loaders should be run
  during cross-compilation.  Native builds can of course use it; cross
  builds can use it if they can run host binaries *and* an executable
  wrapper has been set *and* the target sysroot contains the
  corresponding gdk-pixbuf-query-loaders executable (Ross Burton).
@
text
@$NetBSD: patch-.._vendor_memchr-2.7.6_src_arch_aarch64_memchr.rs,v 1.1 2025/12/08 12:40:15 adam Exp $

Don't try to do neon / SIMD on big-endian aarch64.

--- ../vendor/memchr-2.8.0/src/arch/aarch64/memchr.rs.orig	2025-02-15 20:48:25.871984028 +0000
+++ ../vendor/memchr-2.8.0/src/arch/aarch64/memchr.rs
@@@@ -8,7 +8,7 @@@@ available for `aarch64` targets.)

 macro_rules! defraw {
     ($ty:ident, $find:ident, $start:ident, $end:ident, $($needles:ident),+) => {{
-        #[cfg(target_feature = "neon")]
+        #[cfg(all(target_feature = "neon", target_endian = "little"))]
         {
             use crate::arch::aarch64::neon::memchr::$ty;

@@@@ -19,7 +19,7 @@@@ macro_rules! defraw {
             // enabled.
             $ty::new_unchecked($($needles),+).$find($start, $end)
         }
-        #[cfg(not(target_feature = "neon"))]
+        #[cfg(not(all(target_feature = "neon", target_endian = "little")))]
         {
             use crate::arch::all::memchr::$ty;
@