Re: error when pkg_add'ing

> Having A LOTS of problems in pkg_check usually means something in your > process is REALLY BAD. > > As the guy who wrote (most of) pkg_add/pkg_check, I don't need pkg_check > all that often. Just wanted to say: thanks for writing pkg_add. Don't know if it was by you, but also really

Re: Metronome marking with non-integer value

> Interestingly, and this would have been the topic of my next message, the > resulting MIDI output is always correct whatever \tempo I put (it can be the > same \tempo for all staves). In the example below the top staff is always set > to 4 = 120 and the other staves correctly follow. I'm

[OE-core] [PATCH] bonnie++: New recipe for version 2.0

Newer versions of bonnie get published on . Unfortunately, the new version doesn't compile with g++ 11 which requires *fix-csv2html-data.patch* and configure fails due to cross compilation which gets fixed with *fix-configure-lfs.patch* Signed-off-by:

CCC Hacker Camp 2023 - Ultimi slot per partecipare

Buongiorno a tutti, come di consueto come Inclusive Hacker Framework organizziamo la Italian Hacker Embassy, raduno di Hacker Italiani presso l'hacker camp internazionale CCC CAMP che si terrà in Germania. Per chi volesse fare una mistica esperienza di partecipazione a 5 giorni di convegni,

[nexa] CCC Hacker Camp 2023 - Ultimi slot di partecipazione disponibili

Buongiorno a tutti, come di consueto come Inclusive Hacker Framework organizziamo la Italian Hacker Embassy, raduno di Hacker Italiani presso l'hacker camp internazionale CCC CAMP che si terrà in Germania. Per chi volesse fare una mistica esperienza di partecipazione a 5 giorni di convegni,

[yocto] [yocto-autobuilder-helper][PATCH 3/3] scripts/test_utils.py: update test after BUILD_HISTORY_DIRECTPUSH removal

From: Alexis Lothoré Update getcomparisonbranch unit tests by removing BUILD_HISTORY_DIRECTPUSH entry in fake configuration Signed-off-by: Alexis Lothoré --- scripts/test_utils.py | 29 +++-- 1 file changed, 7 insertions(+), 22 deletions(-) diff --git

[yocto] [yocto-autobuilder-helper][PATCH 2/3] config.json: remove BUILD_HISTORY_DIRECTPUSH

From: Alexis Lothoré Now that BUILD_HISTORY_DIRECTPUSH has been replaced by a hardcoded condition, remove it from config.json Signed-off-by: Alexis Lothoré --- config.json | 1 - 1 file changed, 1 deletion(-) diff --git a/config.json b/config.json index e7f308d0a3f6..f271ffaa402a 100644 ---

[yocto] [yocto-autobuilder-helper][PATCH 0/3] replace BUILD_HISTORY_DIRECTPUSH with hardcoded condition

From: Alexis Lothoré This series is a follow-up to [1], which hot-fixed tests results not being pushed by Autobuilder by enriching the BUILD_HISTORY_DIRECTPUSH variable with mickledore. Since the issue will likely happen for all new releases, this series brings in a better fix (suggested by

[yocto] [yocto-autobuilder-helper][PATCH 1/3] scripts/utils.py: replace BUILD_HISTORY_DIRECTPUSH with hardcoded condition

From: Alexis Lothoré It has been observed that when a new release branch is created, it is quite easy to forget to update the BUILD_HISTORY_DIRECTPUSH variable, which leads to failures in autobuilder like test results not being pushed. Replace the BUILD_HISTORY_DIRECTPUSH usage with a hardcoded

Re: Metronome marking with non-integer value

\set Score.tempoWholesPerMinute = #(ly:make-moment (* 724/10 1/4)) > c > } > \layout { } > \midi { } > } > > If you do not what to do the conversion to rationals 72.4 → 724/10 yourself > you can use (inexact->exact ...), but keep in mind that this will include > rounding err

Metronome marking with non-integer value

Hello, I realised that Lilypond doesn't like it if the metronome value is a non-integer. In the example below, assigning 7 to the voiceAmount variable triggers a 'error: not an unsigned integer'. I tried to construct the metronome number marking as a markup, but without success. Any suggestions?

Re: [tor-relays] (EVENT) Tor Relay Operator Meetup - June 24, 2023 @ 18.00 UTC

On Samstag, 24. Juni 2023 18:03:47 CEST li...@for-privacy.net wrote: > On Dienstag, 20. Juni 2023 23:01:23 CEST gus wrote: > > Just a friendly reminder that the Relay Operator meetup will happen this > > Saturday, June 24 at 18 UTC. > > > > ## Agenda > > > > 1. Announcements > > > > - Tor

Re: [tor-relays] (EVENT) Tor Relay Operator Meetup - June 24, 2023 @ 18.00 UTC

On Dienstag, 20. Juni 2023 23:01:23 CEST gus wrote: > Just a friendly reminder that the Relay Operator meetup will happen this > Saturday, June 24 at 18 UTC. > > ## Agenda > > 1. Announcements > - Tor Relay Operators meetup @ CCCamp 2023! > - More unrestricted snowflake proxies are needed >

Re: clef bass_16

On Fri, 23 Jun 2023 at 12:24, Valentin Petzel wrote: > > To be more general the clef modifier specifies a shift in steps where we start > with 1 as unison. So as an octave is 7 steps n octaves will have a shift of > 7*n, but we will add a 1 as we start with 1 = unison, which gives 0+1 = 1, 7+1 >

Re: [PATCH 2/2] arm: Add support for MVE Tail-Predicated Low Overhead Loops

+ /* In order to find out if the loop is of type A or B above look for the + loop counter: it will either be incrementing by one per iteration or + it will be decrementing by num_of_lanes. We can find the loop counter + in the condition at the end of the loop. */ + rtx_insn

Re: [PATCH 2/2] arm: Add support for MVE Tail-Predicated Low Overhead Loops

+ if (insn != arm_mve_get_loop_vctp (body)) +{ probably a good idea to invert the condition here and return false, helps reducing the indenting in this function. + /* Starting from the current insn, scan backwards through the insn + chain until BB_HEAD: "for each insn in

Re: [OE-core] [PATCH 4/9] runqemu-ifup: remove only our taps

On 22 June 2023 19:01, openembedded-core@lists.openembedded.org wrote: > If there are other tap interfaces than the interfaces created by the > runqemu-* scripts, these interfaces are not ignored. This is now fixed > by filtering the interfaces for a specific prefix in the interface name. > >

Re: [OE-core] [PATCH 1/9] runqemu-ifup: remove uid parameter

On 22 June 2023 19:01, openembedded-core@lists.openembedded.org wrote: > ip tuntap does not need the uid, it was an unused variable/parameter. > Backward compatibility should be fine. > > Signed-off-by: Adrian Freihofer > --- > scripts/runqemu-ifup | 13 - > 1 file changed, 8

Re: [PATCH 2/2] arm: Add support for MVE Tail-Predicated Low Overhead Loops

Some comments below, all quite minor. I'll continue to review tomorrow, I need a fresher brain for arm_mve_check_df_chain_back_for_implic_predic ;) +static int +arm_mve_get_vctp_lanes (rtx x) +{ + if (GET_CODE (x) == SET && GET_CODE (XEXP (x, 1)) == UNSPEC + && (XINT (XEXP (x, 1), 1) ==

Re: Vertical Spacing with Tuplets and Lyrics

On Wed, 21 Jun 2023 at 00:33, Jean Abou Samra wrote: > > Le mardi 20 juin 2023 à 23:44 +0300, Lib Lists a écrit : > > I think the problem is caused by Lilypond putting too many systems on the > page (have no idea why). > > The precise positioning of grobs such as tu

Re: Vertical Spacing with Tuplets and Lyrics

Maybe even better than writing explicitly the number of systems per page, \paper { page-breaking-system-system-spacing.padding = 2 } (https://lilypond.org/doc/v2.25/Documentation/notation/paper-variables-for-page-breaking) seems to work. On Tue, 20 Jun 2023 at 23:44, Lib Lists wrote: > >

Re: Vertical Spacing with Tuplets and Lyrics

On Tue, 20 Jun 2023 at 22:18, Mogens Lemvig Hansen wrote: > > It struck we as weird to put the lyrics inside the DrumStaff, so I tried > something closer to what I would have done for a choir: > > \score { > > << > > \new DrumStaff << > > \new DrumVoice { \voiceOne \CyBars } > >

Re: Grace note spacing & alignment in score

oing to submit a bug report about the collision issues, but it > appears that someone already did so about 10 years ago: > https://gitlab.com/lilypond/lilypond/-/issues/2630 > > Take care, > > Mike Seifert > > > On Jun 15, 2023, at 12:54 PM, Lib L

Re: dvmrpd start causes kernel panic: assertion failed

On Tue, Jun 13, 2023 at 03:12:01PM +0300, Vitaliy Makkoveev wrote: > On Tue, Jun 13, 2023 at 10:04:35AM +0200, Why 42? The lists account. wrote: > So, you tried this diff, and it fixed panic? > > > The system is running the 7.3 release, can I apply that patch directly &g

Re: After update, vim reports undefined symbols in libruby32.so

On Tue, Jun 13, 2023 at 09:37:32AM +0200, Theo Buehler wrote: > ... > That's because libruby32 did not link explicitly against libc++abi, which > is now needed on aarch64 and amd64 for the Rust-based YJIT compiler. > > Fixed in this commit: >

Re: recent malloc changes

On Sun, Jun 18, 2023 at 04:46:46PM +0200, Why 42? The lists account. wrote: > Jun 18 16:18:23 mjoelnir mdnsd: startup > Jun 18 16:18:23 mjoelnir mdnsd: fatal: bind: Address already in use > Jun 18 16:23:02 mjoelnir mdnsd: startup > Jun 18 16:23:02 mjoelnir mdnsd: fatal: bind: Add

Re: recent malloc changes

On Sun, Jun 18, 2023 at 03:34:27PM +0200, Otto Moerbeek wrote: > So what's in your malloc options? Er, nothing: mjoelnir:robb 18.06 15:57:29 [$?==1]# echo $MALLOC_OPTIONS mjoelnir:robb 18.06 15:57:40 # echo $MALLOC_OPTIONS | cat -vet $ mjoelnir:robb 18.06 15:59:25 [$?==1]# unset

Re: recent malloc changes

On Sun, Jun 04, 2023 at 01:03:14PM +0200, Otto Moerbeek wrote: > Hello, > > In the last few weeks a series of mallocs diff have been committed. > The last one today. That one allows malloc to detect more cases of > write-after-free. While that is a good thing, it might uncover latent > bugs in

CCC Camp 2023 e Last Call per i biglietti 24 giugno 12.00

Il CCC Hacker Camp 2023 si avvicina e Italian Hackers Embassy ci sarà! Per unirsi al gruppo e contribuire: https://t.me/italianembassycongress Sabato 24 alle 12.00 è l'ultima occasione per avere un biglietto -> https://events.ccc.de/2023/05/29/camp23-presale/#camp23-presale-en -naif

[nexa] CCC Hacker Camp 2023 e Italian Hackers Embassy

Il CCC Hacker Camp 2023 si avvicina e Italian Hackers Embassy ci sarà! Per unirsi al gruppo e contribuire: https://t.me/italianembassycongress Sabato 24 alle 12.00 è l'ultima occasione per avere un biglietto -> https://events.ccc.de/2023/05/29/camp23-presale/#camp23-presale-en -naif

Re: [gentoo-user] Loading modules prevents shutdown

On 17/06/2023 12:57, dhk wrote: Thanks for the tips.  After spending a lot of time on and off for a few weeks trying to keep /lib/modules on its own partition, it just did not work right; the system was scrapped and rebuilt per the trivial solution with /lib/modules on the root partition.  Now

Fedora on a 2015 iMac?

I have a 27" late 2015 iMac with i5 processor and 16 GB of RAM. It runs El Capitan just fine after wiping the drive and doing an Internet install. This would make a fabulous Fedora workstation! However, I have had trouble getting Fedora installer to run much at all. I have an F38 install

Re: [yocto] [yocto-autobuilder-helper][PATCH 0/3] fix test results storage for mickledore

On 6/16/23 18:30, Richard Purdie wrote: > On Fri, 2023-06-16 at 16:58 +0200, Alexis Lothoré wrote: >> On 6/15/23 22:34, Alexis Lothoré wrote: >>> Hello Richard, Michael, >>> On 6/15/23 15:41, Richard Purdie wrote: On Wed, 2023-06-14 at 10:56 +0200, Alexis Lothoré via

Re: [yocto] [yocto-autobuilder-helper][PATCH 0/3] fix test results storage for mickledore

On 6/15/23 22:34, Alexis Lothoré wrote: > Hello Richard, Michael, > On 6/15/23 15:41, Richard Purdie wrote: >> On Wed, 2023-06-14 at 10:56 +0200, Alexis Lothoré via lists.yoctoproject.org >> wrote: >>> From: Alexis Lothoré >>> >>> There must be a more robust rework to do (because the issue will

Re: [yocto] [yocto-autobuilder-helper][PATCH 0/3] fix test results storage for mickledore

Hello Richard, Michael, On 6/15/23 15:41, Richard Purdie wrote: > On Wed, 2023-06-14 at 10:56 +0200, Alexis Lothoré via lists.yoctoproject.org > wrote: >> From: Alexis Lothoré >> >> There must be a more robust rework to do (because the issue will likely >> happen on each major delivery), but I

Re: Grace note spacing & alignment in score

Hi, Here is a hack, and among the various things to be fixed, the beam thickness of the fake grace notes needs to be checked more carefully against the 'real' grace notes. I calculated the starting point of the fake grace according to the percussion part, so it begins on the upbeat of the 3rd

Re: [yocto] [yocto-autobuilder-helper][PATCH 0/3] fix test results storage for mickledore

On 6/14/23 12:31, Richard Purdie wrote: > On Wed, 2023-06-14 at 10:56 +0200, Alexis Lothoré via > lists.yoctoproject.org wrote: >> From: Alexis Lothoré >> >> This series is a follow-up for the 4.3_M1.rc1 regression report issue. >> >> It has been observed that the report is empty. This issue is

[yocto] [yocto-autobuilder-helper][PATCH 0/3] fix test results storage for mickledore

From: Alexis Lothoré This series is a follow-up for the 4.3_M1.rc1 regression report issue. It has been observed that the report is empty. This issue is linked to configuration description in yocto-autobuilder-helper, and has been identified through the following steps: - empty report is

[yocto] [yocto-autobuilder-helper][PATCH 3/3] config.json: add mickledore as direct push branch for test results

From: Alexis Lothoré Now that mickledore is released, builds are executed on mickeldore release branch. If not properly described in config.json, it will be considered a "work" branch, and as a consequence test results will not be pushed onto test results git repository Add mickeldore entry in

[yocto] [yocto-autobuilder-helper][PATCH 1/3] scripts/send-qa-email: use logger instead of raw prints

From: Alexis Lothoré As for other scripts in yocto-autobuilder-helper or oecore, use python logger class instead of raw print calls to allow log level distinction Signed-off-by: Alexis Lothoré --- scripts/send_qa_email.py | 15 ++- 1 file changed, 10 insertions(+), 5 deletions(-)

[yocto] [yocto-autobuilder-helper][PATCH 2/3] scripts/send-qa-email: print warning when test results are not stored

From: Alexis Lothoré Tests results push command depends on basebranch and comparebranch variables, which are computed based on config.json content. If this file is not in sync with current release branch, tests results will be properly stored in git directory but not pushed onto test results

Re: Compilation time (was: Generate \scaleDurations procedurally)

Dear Jean (and Valentin!), thank you so much! The page breaker was the problem, and after applying your fix the compilation time on my machine is around 3 minutes. I'll soon be able to finish the score, just need to fix the duration ratio and the layout. Again, thank you! Lib P.S. I just found an

Re: [gentoo-user] trying to get sd card reader to work

On 13/06/2023 03:01, John Blinka wrote: Good to know it all works, but if you're sticking a new card in an old reader, they may not be compatible. Don’t know what constitutes new/old, but these are <1 year old cards. Satisfied with empiric evidence that it all works. Have written mp3

Re: dvmrpd start causes kernel panic: assertion failed

On Mon, Jun 12, 2023 at 11:56:43PM +0300, Vitaliy Makkoveev wrote: > ... > We have missing kernel lock around (*if_sysctl)(). Diff below should fix > it. > > Index: sys/netinet/ip_mroute.c > === > RCS file:

Compilation time (was: Generate \scaleDurations procedurally)

Hello, When trying to compile the complete score of the piece below (88 staves and 120 quarter notes), I noticed it was taking many hours (I didn't finish the compilation). Trying with shorter versions, I got the following compilation times: - 2x quarter notes -> 16.7", - 4x quarter notes ->

Re: dvmrpd start causes kernel panic: assertion failed

On Wed, Jun 07, 2023 at 03:50:29PM +0300, Vitaliy Makkoveev wrote: > > ... > > Please, share your dvmrpd.conf. > > > > Also, you could try to use ktrace to provide some additional info. Hi Again, On site I had to power cycle the ThinkPad to be able to get control. The contents of the

Re: [tor-relays] Comcast blocks ALL traffic with tor relays

On Sonntag, 11. Juni 2023 13:46:06 CEST xmrk2 via tor-relays wrote: > Background: I am running a lightning node, lightning is a layer 2 protocol > to scale Bitcoin. Lightning nodes need to be connected to each other > ideally 24/7. I was contacted by the operator of another Lightning node, >

Re: [PATCH] inline: improve internal function costs

On 05/06/2023 04:04, Jan Hubicka wrote: On Thu, 1 Jun 2023, Andre Vieira (lists) wrote: Hi, This is a follow-up of the internal function patch to add widening and narrowing patterns. This patch improves the inliner cost estimation for internal functions. I have no idea why calls

Re: How to generate \scaleDurations values procedurally

On Mon, 12 Jun 2023 at 12:44, Jean Abou Samra wrote: > > [Adding back the list] Oops, thank you! > > Le lundi 12 juin 2023 à 12:23 +0200, Lib Lists a écrit : > > > On Mon, 12 Jun 2023 at 10:58, Jean Abou Samra > > <[j...@abou-samra.fr](mailto:j...@abou-samra.

Re: How to generate \scaleDurations values procedurally

On Mon, 12 Jun 2023 at 00:08, Jean Abou Samra wrote: > > Le dimanche 11 juin 2023 à 23:55 +0200, Lib Lists a écrit : > > Hello, I'm (re)working on a series of pieces for player piano. I'd like to > find a way to generate all the \scaleDurations values so that I don't have to >

How to generate \scaleDurations values procedurally

Hello, I'm (re)working on a series of pieces for player piano. I'd like to find a way to generate all the \scaleDurations values so that I don't have to type them by hand. In the example below they follow a simple pattern (60/60k 60/59, 60/58, etc.). Unfortunately my knowledge of Scheme is very

After update, vim reports undefined symbols in libruby32.so

Hi All, FYI, After running "sysupgrade -s" + "pkg_add -u" earlier today, I now see these messages when I exit vim: mjoelnir:awk 11.06 18:42:45 % vi substrtest.awk ... vim:/usr/local/lib/libruby32.so: undefined symbol '_Unwind_Backtrace' vim:/usr/local/lib/libruby32.so: undefined symbol

Re: dvmrpd start causes kernel panic: assertion failed

On Wed, Jun 07, 2023 at 03:50:29PM +0300, Vitaliy Makkoveev wrote: > > Please, share your dvmrpd.conf. > > > > Also, you could try to use ktrace to provide some additional info. Hi, Thanks for responding, the system is some 30Km away and, er, crashed. But maybe I will get there tomorrow. I

Openscape for iOS?

Hi all, I had a link in twitter that opened to a page telling you about Openscape and asking to install test flight and then install. I did this, but when I went looking for a link it said app wasn't available in my country. TIA. I know this is wrong since I have it -- The following

[OE-core] [PATCH 2/2] runqemu-ifupdown/get-tapdevs: Add support for ip tuntap

The *ip* command supports the creation and destruction of TAP devices since 2009 and might be more likely installed on systems then *tunctl*. Therefore it should be tried to setup or teardown the TAP interface with *ip* before falling back to *tunctl*.

[OE-core] [PATCH 1/2] runqemu-gen-tapdevs: Refactoring

The changes are mostly about early exit which causes indentation changes; check with `git diff -w`. Another change is the check for ip by simply calling it and deciding upon the exit code, if it's fine or not. Signed-off-by: Jörg Sommer --- scripts/runqemu-gen-tapdevs | 77

[OE-core] Fw: [poky] [PATCH] runqemu-ifupdown: Add support for ip tuntap

Sorry, I have to resend this message, because I wasn't subscribed to oe-core. From: Jörg Sommer Sent: Friday, 9 June 2023 09:30 To: Richard Purdie ; p...@lists.yoctoproject.org ; openembedded-core@lists.openembedded.org Subject: Re: [poky] [PATCH]

Re: [OE-Core][PATCH v3 4/4] core-image-ptest: append ptest directory to artifacts list

Hi Mikko, On 6/9/23 08:52, Mikko Rapeli wrote: > Hi, > > On Fri, Jun 09, 2023 at 08:48:02AM +0200, Alexis Lothoré via > lists.openembedded.org wrote: >> From: Alexis Lothoré >> >> TESTIMAGE_FAILED_QA_ARTIFACTS is defined in testimage.bbclass with a >> minimal list of files to retrieve when a

[OE-Core][PATCH v3 4/4] core-image-ptest: append ptest directory to artifacts list

From: Alexis Lothoré TESTIMAGE_FAILED_QA_ARTIFACTS is defined in testimage.bbclass with a minimal list of files to retrieve when a test fail. By appending the ptest directory only in core-image-ptest.bb, thanks to multiconfig feature used in the recipe, only failing ptests will lead to

[OE-Core][PATCH v3 1/4] oeqa/core/runner: add helper to know about expected failures

From: Alexis Lothoré Testing framework currently uses the unittest.expectedFailure decorator for tests that can have intermittent failures (see PTEST_EXPECT_FAILURE = "1") in core-image-ptest.bb. While it allows upper layers to run tests without failing on "fragile" tests, it prevents those from

[OE-Core][PATCH v3 2/4] oeqa/target/ssh: update options for SCP

From: Alexis Lothoré By default scp expects files. Passing -r option allows to copy directories too Signed-off-by: Alexis Lothoré --- Changes since v1: - drop legacy scp protocol option --- meta/lib/oeqa/core/target/ssh.py | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git

[OE-Core][PATCH v3 3/4] testimage: implement test artifacts retriever for failing tests

From: Alexis Lothoré Add a basic artifacts retrievers in testimage class which: - triggers when at least one runtime test fails but tests execution encountered no major issue - reads a list of paths to retrieve from TESTIMAGE_FAILED_QA_ARTIFACTS - checks for artifacts presence on target -

[OE-Core][PATCH v3 0/4] add failed tests artifacts retriever

From: Alexis Lothoré This series is a proposal to bring in an "artifact retriever" to ease debugging when some runtime tests fails. This is a follow-up to the v2 ([1]) and its corresponding RFC ([2]), which in turn is a proposal to address general debugging issues like [3] The main change is

Re: [PATCH v5] MIPS: Add speculation_barrier support

On 01/06/2023 05:26, YunQiang Su wrote: speculation_barrier for MIPS needs sync+jr.hb (r2+), so we implement __speculation_barrier in libgcc, like arm32 does. gcc/ChangeLog: * config/mips/mips-protos.h (mips_emit_speculation_barrier): New prototype. *

Re: [PATCH][GCC][AArch64] convert some patterns to new MD syntax

On 08/06/2023 11:00, Tamar Christina via Gcc-patches wrote: Hi All, This converts some patterns in the AArch64 backend to use the new compact syntax. Bootstrapped Regtested on aarch64-none-linux-gnu and no issues. Ok for master? gcc/ChangeLog: * config/aarch64/aarch64.md (arches):

Re: [PATCH v2] machine descriptor: New compact syntax for insn and insn_split in Machine Descriptions.

On 08/06/2023 11:29, Richard Earnshaw (lists) via Gcc-patches wrote: On 08/06/2023 11:12, Andreas Schwab wrote: On Jun 08 2023, Tamar Christina via Gcc-patches wrote: @@ -713,6 +714,183 @@ you can use @samp{*} inside of a @samp{@@} multi-alternative template:   @end group   @end smallexample

Re: [PATCH v2] machine descriptor: New compact syntax for insn and insn_split in Machine Descriptions.

On 08/06/2023 11:12, Andreas Schwab wrote: On Jun 08 2023, Tamar Christina via Gcc-patches wrote: @@ -713,6 +714,183 @@ you can use @samp{*} inside of a @samp{@@} multi-alternative template: @end group @end smallexample +@node Compact Syntax +@section Compact Syntax +@cindex compact

vect: Don't pass subtype to vect_widened_op_tree where not needed [PR 110142]

Hi, This patch fixes an issue introduced by g:2f482a07365d9f4a94a56edd13b7f01b8f78b5a0, where a subtype was beeing passed to vect_widened_op_tree, when no subtype was to be used. This lead to an errorneous use of IFN_VEC_WIDEN_MINUS. gcc/ChangeLog: * tree-vect-patterns.cc

Re: [OE-Core][PATCH v2 2/2] testimage: implement test artifacts retriever for failing tests

Hello Alexander, Richard, Thanks for the feedback. Indeed my testing setup is quite minimal, so it may not reflect how many files may be pulled in real cases. On 6/7/23 11:20, Alexander Kanavin wrote: > What might work better without code complications is testimage.bbclass > setting only the

Re: [PATCH] modula2: Fix bootstrap

Thanks Jakub! I do need those includes and sorry I broke your bootstrap it didn't show up on my aarch64-unknown-linux-gnu bootstrap, I'm guessing the rules there were just run in a different order. Glad you were able to fix it :) On 06/06/2023 22:28, Jakub Jelinek wrote: Hi! internal-fn.h

[OE-Core][PATCH v2 0/2] add failed tests artifacts retriever

This series is a proposal to bring in an "artifact retriever" to ease debugging when some runtime tests fails. This is a follow-up to the initial version ([1]) and its corresponding RFC ([2]), which in turn is a proposal to address general debugging issues like [3] In the proposed form the

[OE-Core][PATCH v2 1/2] oeqa/target/ssh: update options for SCP

By default scp expects files. Passing -r option allows to copy directories too Signed-off-by: Alexis Lothoré --- Changes since v1: - drop legacy scp protocol option --- meta/lib/oeqa/core/target/ssh.py | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git

[OE-Core][PATCH v2 2/2] testimage: implement test artifacts retriever for failing tests

Add a basic artifacts retrievers in testimage class which: - triggers when at least one runtime test fails but tests execution encountered no major issue - reads a list of paths to retrieve from TESTIMAGE_FAILED_QA_ARTIFACTS - checks for artifacts presence on target - retrieve those files over

Re: [OE-Core][RFC][PATCH 3/3] testimage: implement test artifacts retriever for failing tests

Hi Mikko, sorry for late reply, and thanks for the additional feedback On 6/2/23 15:07, Mikko Rapeli wrote: > Hi, > > These changes are an improvement, but based on my experience in product test > automation, > instead of collecting logs after testing is completed, it is better to > capture

Re: [PATCH v2] machine descriptor: New compact syntax for insn and insn_split in Machine Descriptions.

e possible to define things like "type" in this way. You also want it for the case where every alternative takes the same value, eg the "predicable - yes" attr. R. However you're right, I could simply say that you must omit the set_attr in attrs and just merge the two lists? I think that's what you were alluding to? Yeah, that's right. Or just concatenate them and rely on later error checking (which should give reasonable diagnostics). Thanks, Richard

Re: [tor-relays] «Possible compression bomb» from Authority?

On Samstag, 3. Juni 2023 18:18:46 CEST Tschador wrote: > today I found this warning in the log of my relay > Jun 03 04:04:33.000 [warn] Possible compression bomb; abandoning stream. > What does this mean? A simple log message that the tord didn't unpack a Zip Bomp. DDOS protection in the Tor

GNU Tools Cauldron 2023

We are pleased to invite you all to the next GNU Tools Cauldron, taking place in Cambridge, UK, on September 22-24, 2023. As for the previous instances, we have setup a wiki page for details: https://gcc.gnu.org/wiki/cauldron2023 Like last year, we are having to charge for attendance.  We are

Re: [OE-Core][RFC][PATCH 1/3] oeqa/target/ssh: update options for SCP

On 6/2/23 14:02, Richard Purdie wrote: > On Fri, 2023-06-02 at 11:50 +0200, Alexis Lothoré via > lists.openembedded.org wrote: >> Add two options for SCP: >> - by default scp expects sftp server to be available on target, which is >> not always true (e.g: core-image-minimal image). Pass -O to

Re: [OE-Core][RFC][PATCH 2/3] testimage: shut down DUT later

Hello Richard, On 6/2/23 13:55, Richard Purdie wrote: > On Fri, 2023-06-02 at 11:50 +0200, Alexis Lothoré via > lists.openembedded.org wrote: >> Move target stop (for Qemu targets: qemu image stop) later in testimage >> main function, especially _after_ having access to general test results, to >>

Re: [OE-Core][RFC][PATCH 3/3] testimage: implement test artifacts retriever for failing tests

Hello Alexander, Mikko, On 6/2/23 13:52, Mikko Rapeli wrote: > Hi, > > On Fri, Jun 02, 2023 at 01:46:03PM +0200, Alexander Kanavin wrote: >> On Fri, 2 Jun 2023 at 11:50, Alexis Lothoré via lists.openembedded.org >> wrote: >>> +# When any test fails, if path to an artifacts configuration

[OE-Core][RFC][PATCH 3/3] testimage: implement test artifacts retriever for failing tests

Add a basic artifacts retrievers in testimage class which: - triggers when at least one runtime test fails - reads a list of files to retrieve from ARTIFACTS_LIST_PATH - retrieve those files over scp thanks to existing ssh class - store those files in an "artifacts" directory in "tmp/log/oeqa/"

[OE-Core][RFC][PATCH 2/3] testimage: shut down DUT later

Move target stop (for Qemu targets: qemu image stop) later in testimage main function, especially _after_ having access to general test results, to allow executing some other actions (like retrieving some files) on DUT depending on test results (e.g. : retrieve some log files) Signed-off-by:

[OE-Core][RFC][PATCH 0/3] add failed test artifacts retriever

This series is a proposal to bring in an "artifact retriever" to ease debugging when some runtime tests fails. This is a follow-up to corresponding RFC ([1]), which in turn is a proposal to address general debugging issues like [2] In the proposed form the retriever is pretty simple/dumb: it

[OE-Core][RFC][PATCH 1/3] oeqa/target/ssh: update options for SCP

Add two options for SCP: - by default scp expects sftp server to be available on target, which is not always true (e.g: core-image-minimal image). Pass -O to force SCP to fallback to legacy SCP protocol - by default scp expects files. Passing -r option allows to copy directories too

Re: [PATCH] inline: improve internal function costs

On 02/06/2023 10:13, Richard Biener wrote: On Thu, 1 Jun 2023, Andre Vieira (lists) wrote: Hi, This is a follow-up of the internal function patch to add widening and narrowing patterns. This patch improves the inliner cost estimation for internal functions. I have no idea why calls

[PATCH] gimple-range: implement widen plus range

Hi, This patch adds gimple-range information for the new IFN_VEC_WIDEN_PLUS* internal functions, identical to what VEC_WIDEN_PLUS did. Bootstrapped and regression tested on aarch64-unknown-linux-gnu. gcc/ChangeLog: * gimple-range-op.cc (gimple_range_op_handler::maybe_non_standard):

[PATCH] inline: improve internal function costs

Hi, This is a follow-up of the internal function patch to add widening and narrowing patterns. This patch improves the inliner cost estimation for internal functions. Bootstrapped and regression tested on aarch64-unknown-linux-gnu. gcc/ChangeLog: * ipa-fnsummary.cc

Re: [PATCH 2/3] Refactor widen_plus as internal_fn

LUS is being used. * gcc.target/aarch64/vect-widen-sub.c: Test that new IFN_VEC_WIDEN_MINUS is being used. On 22/05/2023 14:06, Richard Biener wrote: On Thu, 18 May 2023, Andre Vieira (lists) wrote: How about this? Not sure about the DEF_INTERNAL documentation I rewrote in int

Re: Proportional duration and cross-staff notation

gt; > \clef bass > > \stemUp b8[ c' \up c' b] > > \down b8[ \up c' b] > > \down c'[ \up c'] > > \down b8 \up c' b > >} > > > >>> > > > > \layout { > > \context { > >\Score > >proport

Re: Frescobaldi issue 16: .ly is missing by saving

Just checked on macOS Ventura 13.4 and Frescobaldi adds the .ly extension automatically. Cheers, Lib On Mon, 29 May 2023 at 22:52, Federico Bruni wrote: > > Hi all > > I'm wondering if we can close this old Frescobaldi issue: > https://github.com/frescobaldi/frescobaldi/issues/16 > > In some

[OE-core] [PATCH] pybootchartgui: show elapsed time for each task

From: Mauro Queiros Currently, finding the elapsed time of each task in buildtimes.svg is a manual effort of checking the top axis and finding and subtracting the end and start time of the task. This change adds the elapsed time for each task, so that manual effort of comparing start/end time

Re: Changing distance between chord suffixes

Indeed chordNameSeparator is responsible for the space between suffixes. Solved as follows: \version "2.25.5" \chords{ des:maj7.5+ fis:7.5+.9+.11+ } \layout { \context { \ChordNames chordNameSeparator = #(make-hspace-markup 0.2) } } On Sat, 27 May 2023 at 17:59, Lib Li

Changing distance between chord suffixes

Hello, in the following example (see attached edited pdf) I'd like to reduce the distance between the suffixes. It looks like the distance between the root and the first suffix is smaller than the distances between the following suffixes. \version "2.25.5" \chords{ des:maj7.5+ fis:7.5+.9+.11+ }

Re: Changing accidental size and alignment in chord symbols

markup list. It's not yet perfect, as I'd wish the sharp sign to be still smaller, but satisfactory enough. See screenshot 'before' and 'after'. Cheers, Lib On Sat, 27 May 2023 at 12:49, Lib Lists wrote: > > Replying to myself, as it might help someone else to give me some hints. > I

Re: Changing accidental size and alignment in chord symbols

cidentals.sharp"))) However, I didn't manage to change the size of the accidentals. If anyone could point me in the right direction it would be great! Bear in mind, my knowledge of Scheme is primitive to say the least. Best regards, Lib On Fri, 26 May 2023 at 10:31, Lib Lists wrote: > > I

Changing accidental size and alignment in chord symbols

I'd like to change the size of the accidentals and their alignment in chord symbols. Here a MWE: \version "2.25.5" \chords { aes2 cis } Specifically, I'd like to have all the flats smaller, and the sharps smaller and horizontally center-aligned with the root note name. I checked the manual

Re: Changing half-diminished symbol size

On Fri, 26 May 2023 at 03:16, wrote: > > > I'd like to change the size of the half-diminished chord symbol, but I > > cannot find a way to do it. > > > > \version "2.25.5" > > \chords { > > \set majorSevenSymbol = \markup { \override #'(thickness . 2) > > \triangle ##f "7" } > > c4:maj7 a:min7.5-

Changing half-diminished symbol size

I'd like to change the size of the half-diminished chord symbol, but I cannot find a way to do it. \version "2.25.5" \chords { \set majorSevenSymbol = \markup { \override #'(thickness . 2) \triangle ##f "7" } c4:maj7 a:min7.5- } I'm aware there's not a halfDimishedSymbol, but I cannot

Re: Wrong cost computation / conclusion ins insn combine?

On 23/05/2023 19:41, Georg-Johann Lay wrote: For some time now I am staring at the following test case and what combine does with it: typedef struct {     unsigned b0 : 1;     unsigned b1 : 1;     unsigned b2 : 1;     unsigned b3 : 1;     unsigned b4 : 1;     unsigned b5 : 1;    

[ceph-users] Timeout in Dashboard

Hey all, im facing a "minor" problem. I do not always get results when going to the dashboard, under Block->Images in the tab Images or Namespaces. The little refresh button will keep spinning and sometimes after several minutes it will finally show something. That is odd, because from the

<    2   3   4   5   6   7   8   9   10   11   >