similar to: Multiple readfile oddities, newlines etc

On Tue, 18 Oct 2016, Pete Mundy wrote: > If you want to know what is _really_ in that file (including all > invisible characters and anything else that wc etc might not count), > pipe it through 'hexdump'. > > cat?/home/test/feature-1.txt | hexdump Or just: hexdump /home/test/feature-1.txt -- Thanks in advance,

Hi, I have a data.frame that looks something like this. feature 5637 ? ? ? ? ? ? ? ?1321N1 feature1 -0.568750616 -0.934748758 feature2 -0.913080902 -0.941455172 feature3 0.442477294 -0.257921866 I want to change it to look like this. feature ? ? ?cell.line ? ? value feature1 5637 -0.568750616 feature2 5637 -0.913080902 feature3 5637 0.442477294 feature1 1321N1

I'm trying to enable/disable a target feature through clang. Here is how my target looks like // Esencia subtarget features //===----------------------------------------------------------------------===// def FeatureMul : SubtargetFeature<"mul", "HasMul", "true", "Enable hardware multiplier">; def FeatureDiv

Hello! Just installed asterisk 13.2.0 and see many such messages in log, I see them in console during calls, really something like this: -- Executing [6166 at kanbaikal:2] Dial("OOH323/kanbaikal-6", "SIP/6166 at asterisk") in new stack == Using SIP RTP TOS bits 184 == Using SIP RTP CoS mark 5 -- Called SIP/6166 at asterisk > 0x7fa9d4007660 --

05.03.2015 11:42, Dmitry Melekhov ?????: > 05.03.2015 11:29, Dmitry Melekhov ?????: >> Hello! >> >> Just installed asterisk 13.2.0 and see many such messages in log, I >> see them in console during calls, really something like this: >> >> >> -- Executing [6166 at kanbaikal:2] Dial("OOH323/kanbaikal-6", >> "SIP/6166 at

Dear all, I have a data frame, which looks like this: Subject | Block | Trial | Feature1 | Feature2 .... 1 | 1 | 1 | ... | ... 1 | 1 | 2 | ... | ... 1 | 2 | 1 | ... | ... 1 | 2 | 2 | ... | ... 1 | 3 | 1 | ... | ... ...| ...| ...| ... | ... Can I remove the "Trial" column by averaging all the rows and without using a "for loop"? At the end my data frame should look like

2023-11-08 18:14:13] ERROR[571246][C-000017e2] : Got 19 backtrace records # 0: [0x5bd18a] asterisk utils.c:2800 __ast_assert_failed() # 1: [0x4618e3] asterisk astobj2.c:589 __ao2_ref() # 2: [0x58e660] asterisk stasis_cache.c:824 update_create() # 3: [0x58efed] asterisk stasis_cache.c:903 caching_topic_exec() # 4: [0x586b90] asterisk stasis.c:1380 dispatch_message() # 5: [inlined] asterisk

Hello, I am using an ARI dialer for my applications and since my last upgrade to Ver. 13.29.2 from 13.23.1 I am getting this strange bug from the ARI debugger: Debugging on all applications enabled <--- ARI request received from: x.x.x.x:63036 ---> HOST: x.x.x.x:8088 content-type: application/json authorization: Basic xxxx content-length: 265 body: { "context":

Hello Asterisk list, I've facing a memory allocation issue that happens occasionally but on a consistent basis. The problem happens as follow, suddenly Asterisk starts consuming a lot of memory, in a rate of more than 1GB per hour. Kernel will eventually kill it via the OOM killer when memory is really exausted... This situation does not generate backtrace because Asterisk is responsive

Is there a way to enable/disable target features through clang? I found this, https://github.com/avr-llvm/llvm/issues/9, but this seems to be talking about llc -mattr=+feature1,-feature2... Is there something equivalent for clang? -- Rail Shafigulin Software Engineer Esencia Technologies -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, I'd like to propose extending the supported syntax for AssemblerPredicates to allow sets of SubtargetFeatures to be listed, but where only one in the list has to be enabled for the predicate to be true. The condition string which forms a AssemblerPredicate already allows multiple features to be defined, separated by commas, and this means all of these features must be present. For

I'm not mathematically gifted, but shouldn't 957%60 be 15 remainder 57? Google and my desktop calculator certainly think so. So where am I going wrong here? The following code exten => 7,1,Verbose(Context: ${CONTEXT} Exten:${EXTEN}) same => n,Set(myNum=957) same => n,Set(sec=$[REMAINDER(${myNum},60)]) same => n,Set(sec=$[ABS(${sec})]) same =>

On Wed, Oct 10, 2018 at 01:54:33PM -0500, Segher Boessenkool wrote: > It would be great to hear from kernel people if it works adequately for > what you guys want it for :-) Sure, ping me when you have the final version and I'll try to build gcc with it and do some size comparisons. Thx. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the

On Wed, Oct 10, 2018 at 01:54:33PM -0500, Segher Boessenkool wrote: > It would be great to hear from kernel people if it works adequately for > what you guys want it for :-) Sure, ping me when you have the final version and I'll try to build gcc with it and do some size comparisons. Thx. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the

05.03.2015 11:29, Dmitry Melekhov ?????: > Hello! > > Just installed asterisk 13.2.0 and see many such messages in log, I > see them in console during calls, really something like this: > > > -- Executing [6166 at kanbaikal:2] Dial("OOH323/kanbaikal-6", > "SIP/6166 at asterisk") in new stack > == Using SIP RTP TOS bits 184 > == Using SIP

On Thu, Mar 5, 2015 at 2:29 AM, Dmitry Melekhov <dm at belkam.com> wrote: > Hello! > > Just installed asterisk 13.2.0 and see many such messages in log, I see them > in console during calls, really something like this: > > > -- Executing [6166 at kanbaikal:2] Dial("OOH323/kanbaikal-6", > "SIP/6166 at asterisk") in new stack > == Using SIP

On Tue, Mar 10, 2015 at 5:00 AM, Dmitry Melekhov <dm at belkam.com> wrote: > 05.03.2015 11:42, Dmitry Melekhov ?????: > >> 05.03.2015 11:29, Dmitry Melekhov ?????: >>> >>> Hello! >>> >>> Just installed asterisk 13.2.0 and see many such messages in log, I see >>> them in console during calls, really something like this: >>>

This changes the pv ops code generation to more closely match reality. For example, instead of: callq *0xffffffff81e3a400 (pv_irq_ops.save_fl) vmlinux will now show: pushfq pop %rax nop nop nop nop nop which is what the runtime version of the code will show in most cases. This idea was suggested by Andy Lutomirski. The benefits are: - For the most common runtime cases

This changes the pv ops code generation to more closely match reality. For example, instead of: callq *0xffffffff81e3a400 (pv_irq_ops.save_fl) vmlinux will now show: pushfq pop %rax nop nop nop nop nop which is what the runtime version of the code will show in most cases. This idea was suggested by Andy Lutomirski. The benefits are: - For the most common runtime cases

The ALTERNATIVE() and ALTERNATIVE_2() macros are GNU assembler macros, which makes them quite inflexible for future changes. Convert them to preprocessor macros. Signed-off-by: Josh Poimboeuf <jpoimboe at redhat.com> --- arch/x86/entry/entry_32.S | 12 +++--- arch/x86/entry/entry_64.S | 10 ++--- arch/x86/entry/entry_64_compat.S | 8 ++--