search for: 19min

...stemctl restart postfix Now Postgrey seems to be running OK. $ systemctl status postgrey ? postgrey.service - Postfix Greylisting Service Loaded: loaded (/usr/lib/systemd/system/postgrey.service; enabled; vendor preset: disabled) Active: active (running) since mer. 2019-06-19 09:39:04 CEST; 19min ago Docs: man:postgrey(8) Process: 5228 ExecStart=/usr/sbin/postgrey --unix=/var/spool/postfix/postgrey/socket --pidfile=/var/run/postgrey.pid --group=postgrey --user=postgrey --greylist-text=Greylisted for %%s seconds --daemonize $POSTGREY_OPTS (code=exited, status=0/SUCCESS) Process: 522...

...how it running and does nmcli > show anything? > systemctl status NetworkManager ? NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2017-02-16 08:19:34 UTC; 2h 19min ago * more stuff * nmcli eth0: connected to Wired connection 1 "Red Hat Virtio network device" ethernet (virtio_net), F2:3C:91:18:8A:7E, hw, mtu 1500 ip4 default, ip6 default inet4 178.79.185.217/24 route4 178.79.187.246/32 inet6 2a01:7e00::825f:e564:ad53:72fc/64 inet6 fe80::a8ad...

...ostgrey seems to be running OK. > > $ systemctl status postgrey > ? postgrey.service - Postfix Greylisting Service > Loaded: loaded (/usr/lib/systemd/system/postgrey.service; enabled; > vendor preset: disabled) > Active: active (running) since mer. 2019-06-19 09:39:04 CEST; 19min > ago > Docs: man:postgrey(8) > Process: 5228 ExecStart=/usr/sbin/postgrey > --unix=/var/spool/postfix/postgrey/socket > --pidfile=/var/run/postgrey.pid --group=postgrey --user=postgrey > --greylist-text=Greylisted for %%s seconds --daemonize $POSTGREY_OPTS > (code=exit...

...tgrey seems to be running OK. > > $ systemctl status postgrey > ? postgrey.service - Postfix Greylisting Service > Loaded: loaded (/usr/lib/systemd/system/postgrey.service; enabled; > vendor preset: disabled) > Active: active (running) since mer. 2019-06-19 09:39:04 CEST; 19min ago > Docs: man:postgrey(8) > Process: 5228 ExecStart=/usr/sbin/postgrey > --unix=/var/spool/postfix/postgrey/socket > --pidfile=/var/run/postgrey.pid --group=postgrey --user=postgrey > --greylist-text=Greylisted for %%s seconds --daemonize $POSTGREY_OPTS > (code=exited,...

...> >> >> systemctl status NetworkManager >> ? NetworkManager.service - Network Manager >> Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; >> vendor preset: enabled) >> Active: active (running) since Thu 2017-02-16 08:19:34 UTC; 2h 19min ago >> >> * more stuff * >> >> nmcli >> eth0: connected to Wired connection 1 >> "Red Hat Virtio network device" >> ethernet (virtio_net), F2:3C:91:18:8A:7E, hw, mtu 1500 >> ip4 default, ip6 default >> i...

...obalISel by default. In particular, Renato and I exchanged offline and he tried doing the switch on some of the bots he maintained and did not see any overhead/problem for that. > Let me know if you disagree. > > > * What is the impact on compile time? > > Negligible: ~5s for a 19min build. (See http://lists.llvm.org/pipermail/llvm-dev/2017-January/109185.html <http://lists.llvm.org/pipermail/llvm-dev/2017-January/109185.html> for the details.) > > > * What is the impact on binary size? > > Negligible: 0 to 1M on a 37M to 104M. (See http://lists.llvm.org...

> If x is a local variable, it will be stored on the stack. So you need an > alloca for it: Aha, I remember this in Kaleidoscope tutorial. So, after the alloca %x can be modified freely (e.g. without adding suffix)? -- View this message in context: http://old.nabble.com/How-to-assign-a-constant-to-a-register--tp29987387p30016496.html Sent from the LLVM - Dev mailing list archive at

...> show anything? >> > > systemctl status NetworkManager > ? NetworkManager.service - Network Manager > Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; > vendor preset: enabled) > Active: active (running) since Thu 2017-02-16 08:19:34 UTC; 2h 19min ago > > * more stuff * > > nmcli > eth0: connected to Wired connection 1 > "Red Hat Virtio network device" > ethernet (virtio_net), F2:3C:91:18:8A:7E, hw, mtu 1500 > ip4 default, ip6 default > inet4 178.79.185.217/24 >...

...nager >>>> ? NetworkManager.service - Network Manager >>>> Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; >>>> enabled; >>>> vendor preset: enabled) >>>> Active: active (running) since Thu 2017-02-16 08:19:34 UTC; 2h 19min >>>> ago >>>> >>>> * more stuff * >>>> >>>> nmcli >>>> eth0: connected to Wired connection 1 >>>> "Red Hat Virtio network device" >>>> ethernet (virtio_net), F2:3C:91:18:8A:7E,...

Hi, If x is a local variable, it will be stored on the stack. So you need an alloca for it: %x = alloca i8 ; <i8*> Then you can just perform a store: Store i8* %x, i8 0 Cheers, James > -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of leledumbo > Sent: 20 October 2010 14:39 > To: llvmdev at

...ctl status NetworkManager >>> ? NetworkManager.service - Network Manager >>> Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; >>> enabled; >>> vendor preset: enabled) >>> Active: active (running) since Thu 2017-02-16 08:19:34 UTC; 2h 19min >>> ago >>> >>> * more stuff * >>> >>> nmcli >>> eth0: connected to Wired connection 1 >>> "Red Hat Virtio network device" >>> ethernet (virtio_net), F2:3C:91:18:8A:7E, hw, mtu 1500 >>>...

...particular, Renato and I exchanged offline and he tried doing the switch on some of the bots he maintained and did not see any overhead/problem for that. >> Let me know if you disagree. >> >> >> * What is the impact on compile time? >> >> Negligible: ~5s for a 19min build. (See http://lists.llvm.org/pipermail/llvm-dev/2017-January/109185.html <http://lists.llvm.org/pipermail/llvm-dev/2017-January/109185.html> for the details.) >> >> >> * What is the impact on binary size? >> >> Negligible: 0 to 1M on a 37M to 104M. (See h...

...Manager.service - Network Manager >>>>>> Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; >>>>>> enabled; >>>>>> vendor preset: enabled) >>>>>> Active: active (running) since Thu 2017-02-16 08:19:34 UTC; 2h 19min >>>>>> ago >>>>>> >>>>>> * more stuff * >>>>>> >>>>>> nmcli >>>>>> eth0: connected to Wired connection 1 >>>>>> "Red Hat Virtio network device" >>&gt...

...t;> ? NetworkManager.service - Network Manager >>>>> Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; >>>>> enabled; >>>>> vendor preset: enabled) >>>>> Active: active (running) since Thu 2017-02-16 08:19:34 UTC; 2h 19min >>>>> ago >>>>> >>>>> * more stuff * >>>>> >>>>> nmcli >>>>> eth0: connected to Wired connection 1 >>>>> "Red Hat Virtio network device" >>>>> ethernet (...

On Wed, Jan 18, 2017 at 9:13 AM David Blaikie via llvm-dev < llvm-dev at lists.llvm.org> wrote: > These concerns sound applicable to the situation when GlobalISel is turned > on by default and has an effect on code generation. > > While it's a library with tests like any other LLVM component I don't see > these concerns as being significantly greater risk than any

On 02/16/2017 02:03 AM, James Hogarth wrote: > On 16 February 2017 at 09:09, Alice Wonder <alice at domblogger.net> wrote: >> On 02/16/2017 12:54 AM, Tony Mountifield wrote: >>> >>> In article <4cbb9dc4-f063-3434-b7a1-d4d0e6581b5e at domblogger.net>, >>> Alice Wonder <alice at domblogger.net> wrote: >>>> >>>>

Hi all, Now, four backends (if I am counting right: X86, ARM, AArch64, AMDGPU) are working on bringing-up GlobalISel, I’d like to switch the default of the LLVM_BUILD_GLOBAL_ISEL variable in CMake, such that the framework gets built by default. ** Impact of Flipping the Switch ** * Upsides * For people developing on GlobalISel, it will: - Simplify the CMake command to type :) - Build/Test